> On Oct 27, 2016, at 7:59 PM, Gene Heskett <ghesk...@shentel.net> wrote: > > At high risk of starting another flame war about network-manager, nuke > that puppy with extreme prejudice.
Don't tell anybody, but that's exactly what I want to do. > Then fix resolv.conf to be a REAL file, it may be a link. Hadn't thought of that -- bears looking into. > Then: > sudo chmod +i /etc/resolv.conf > So nothing can scribble over it. That's the command I was looking for. I didn't know about that one. > Then in the /etc/networking/interfaces file, add: No prob -- eth* is defined there. > sudo service network restart, and your network should just work. From > then on. Thank you very much. > Now this of course isn't going to work if you are carrying a lappy and > expecting to tap the wifi at any Starbucks you pull into. Then you are > truly at the mercy of network-mangler, which might work but usually > doesn't. That's no prob either. It's the servers I'd just as soon worked. There are people who rely on them. > Now, save your flames, I already put on my nomex suit. No flames here :-) Thanks, Gene As far as NMs go, have you looked at WICD? It's on my Debian Jessie XFCE laptop, and it seems relatively OK. It doesn't do anything without being told to, it allows only one interface up at a time (usually a good idea), and it remembers how to get the damn WiFi going. And you can make all those extraneous APs disappear. -- Glenn English -- Glenn English Did you just click Reply? If so, change the send address from gmail to g...@slsware.net
