Interesting. I took a look at mine, and found lrwxrwxrwx 1 root root 29 Aug 8 2016 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
so the thing is now entirely dynamic. I don't know what setting it immutable would do or mean. I'm running xubuntu 16.04.3 LTS On Fri, Oct 27, 2017 at 5:35 AM, Greg Wooledge <wool...@eeg.ccf.org> wrote: > On Fri, Oct 27, 2017 at 01:18:58PM +0100, Darac Marjal wrote: > > Who's saying it must be installed? > > A few people in this thread, though I think they're saying "should" > rather than "must". > > > Maybe I've missed something, but I think > > the consensus in this discussion was that if you want your resolv.conf > to be > > unmanaged/static/administrator-controlled, then don't have resolvconf > > installed. If you have resolvconf installed, then what's the point of > > neutering it with a command? > > Let's review what we've learned so far. > > If you want to make local modifications to /etc/resolv.conf and have > them stick, here are some ways to do it: > > 1) chattr +i /etc/resolv.conf > > 2) Individually configure each daemon that might try to modify the file, > to make it stop doing so. > > 3) Install the resolvconf package, because by doing so you also install > various hacks that modify the behavior of all known Debian daemons, > stopping them from writing to /etc/resolv.conf. > > Then tell resolvconf itself to do nothing by putting resolvconf=NO > in the /etc/resolvconf.conf file. > > -- Kevin O'Gorman #define QUESTION ((bb) || (!bb)) /* Shakespeare */ Please consider the environment before printing this email.
