Re: resolvconf troubles
On Friday 28 October 2016 03:30:30 tomas@tuxteam.de wrote:
> On Thu, Oct 27, 2016 at 09:59:37PM -0400, Gene Heskett wrote:
> > On Thursday 27 October 2016 21:03:21 Glenn English wrote:
>
> [...]
>
> > At high risk of starting another flame war about network-manager,
> > nuke that puppy with extreme prejudice.
>
> I did that ~7 years ago. This was the day I plugged my laptop into the
> Ethernet at a customer's site and NM went "Oh, shiny, a wlan!" and
> *poof* I was out of the customer's network and in a captive coffeeshop
> WLAN.
>
> Enough was enough.
>
> To be fair, though, in my case it's dhclient overwriting my
> resolv.conf at boot. And it's supposed to do it (mobile laptop).
>
> [...]
>
> > sudo chmod +i /etc/resolv.conf
> > So nothing can scribble over it.
>
> This is a trick I use often to answer the question "who is scribbling
> over XXX?". Set immutable and see 'em complain in the logs :-)
In my case, n-m was denied that pleasure, and had the great good sense to
just STHU. I could see it bouncing around in the htop output as it
struggled, but no logs were spammed and my network worked 100%. ISTR
dhcpd wasn't even installed. This was then a trio of ubu 6-04 lts
installs 10 years ago. Now there are 5 wheezy installs here, soon to be
6 I think. I am expecting a raspi-3 Saturday.
This was back in the day when removing it took half the system with it.
Now all the dependencies are gone, and it is removeable, so I thank
$DIETY at every install around the coyote.den. And my local network
Just Works. Any of them has full, unrestricted access to ALL them
innertubes. Whats not to love? :)
> regards
> -- tomás
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: