Re: boot ordering and resolvconf
Don Armstrong wrote:
On Tue, 02 Jul 2013, Tollef Fog Heen wrote:
Automatic processes overwrite explicit admin setups.
If /etc/resolv.conf is a symlink to somewhere else, then it's
appropriate for automatic processes to override it by writing to
"somewhere else". If it's not a symlink, then it shouldn't be
That seems pretty plain, but Ubuntu/Networkmanager routinely ignore this fact.
I'm a bit surprised that this conversation still needs to happen today. It was
a constant annoyance when I was using Ubuntu. (I finally switched to Arch back
in January this year.)
Networkmanager seems to have been the root of most of my complaints; its
authors seem to believe that their code knows better than a machine's sysadmin
how the machine should be operated.
The sensible thing to do is let something like dnsmasq do all resolver
management. I first proposed this change ~5 years ago
It's a topic that comes up perennially.
Providing solutions for other tools, e.g. dhclient or pppd is pretty trivial too.
We're well into the 2nd decade of the 21st century. These problems shouldn't
exist any more.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/