Re:How to take back control of /etc/resolv.conf on Linux (2018)
by xvYXA on Wednesday March 20, 2019 @06:45AM
(#19440766)
I guess the discussion is a bit heated because distros keep breaking stuff that worked 10 years ago.
It would be fine if overall reliability increased, but it does not. I could write more reliable shell scripts for making WiFi or PPP connections than NetworkManager, which sometimes required a reboot before graciously allowing to connect again. Never happens on the command line.
Thank you for describing the status quo, I'll probably look into Slackware or OpenBSD now.
Re:How to take back control of /etc/resolv.conf on Linux (2018)
by zcid on Wednesday March 20, 2019 @07:19AM
(#19440943)
My suggestion for Linux right now is Void Linux. It's clean and minimalist and eschews systemd for runit. It feels a lot like OpenBSD without ports (although the manpages are sadly Linux-like).
Re:How to take back control of /etc/resolv.conf on Linux (2018)
by usr1106 on Wednesday March 20, 2019 @05:17AM
(#19440312)
Actually another daemon that seems to be deeply hardwired into glibc is nscd(8). All applications I have traced recently try to open the nscd socket.
Whether nscd is still installed by any distro by default I don't know. I haven't seen it running for years.
Re:How to take back control of /etc/resolv.conf on Linux (2018)
by esjeon on Wednesday March 20, 2019 @08:42AM
(#19441451)
I don’t see any point of leaving resolved behind once both NM and nsswitch are configured to ignore resolved. Disabling resolved pretty much does a half of the trick without modifying a major system config file anyway.
My only point was if you want "to take control" of your system you first have to look /etc/nsswitch.conf. If "resolve" is before "dns" your /etc/resolv.conf is mostly unused. Any article discussing /etc/resolv.conf without mentioning /etc/nsswitch.conf is very misleading for many users who happen to have systemd-resolved (probably because the distro decided to install and configure it)