On 26/10/17 13:40, Stefan Monnier wrote: >> Given that multiple packages potentially touch/change resolv.conf (at >> least resolvconf and the various DHCP clients), > > That is not true: when resolvconf is installed, *no package* should > (modulo bugs) ever change /etc/resolv.conf. > > Instead all changes go through resolvconf, which only modifies > /run/resolvconf/resolv.conf (and those changes usually get reflected > into /etc/resolv.conf by making it a symlink to that file, but that's > not mandatory). > > Stefan "who thinks resolvconf should always be installed"
I think it would be preferable for every package which wants to write to the resolv.conf file to be required to use the resolvconf package to do so (which is what I, and I think some other people, thought the situation was until we read this thread). Uninstalling the resolvconf package would then mean nothing could write to the resolv.conf file. I've been in the fortunate position that I've never needed to install the resolvconf package and nothing has ever tried to modify my resolv.conf file. I've obviously led a sheltered life. Roger
