On Sat, Nov 04, 2017 at 08:45:59AM +0100, to...@tuxteam.de wrote: > > Most of us fall into two classes: > > A. All static. Nobody changes resolv.conf. All is well. Admin writes > resolv.conf (and /etc/hosts and all). (the "classic") > B. Get IP address via DHCP (dhclient, NetworkManager, whatever else). > Whatever else writes to resolv.conf. User == admin mostly doesn't > even know what resolv.conf means, most of the time. > > Without resolvconf, you're in trouble if there are several agents > caring about resolv.conf, that is, you are in class B and have > e.g. NetworkManager and say dhclient (or some systemd outgrowth, > cough, cough) trying to write to that file. Or you are in an intersection > of A and B (who said they were disjoint? The sysadmin is but an agent > more). In the latter case, you're bound to learn enough about sysadmin > to really decide whether you *want* resolvconf or not. > > Me? I am in Aâ©B. And with no resolvconf. Stefan? Most probably in > the same set. And with resolvconf. > I agree. The intersection situation (which I believe describes my) is why I filed #879949. I small hint would have saved me many hours of frustration. I suspect that it would do the same for others.
Regards, -Roberto -- Roberto C. Sánchez
