3 ms·
I don't want to participate in the discussion whether systemd and systemd-resolved are good or bad or for laymen or not. My only point was if you want "to take
by usr1106 8y ago
I don't want to participate in the discussion whether systemd and systemd-resolved are good or bad or for laymen or not.
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)
- usr1106 8y agoActually 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.
- xvYXA 8y agoI 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.
- zcid 8y agoMy 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).
- esjeon 8y agoI 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.