It is Linux Mint 17.3, which is based on Ubuntu Trusty. So, yes, as far as
I know, it should be the same on a modern Ubuntu distro.

http://manpages.ubuntu.com/manpages/lucid/man8/resolvconf.8.html

-- drewc

On Sat, Mar 26, 2016 at 9:49 AM, Thompson, David <dthompson2@worcester.edu>
wrote:

> On Sat, Mar 26, 2016 at 12:29 PM, Drew C <me@drewc.ca> wrote:
> >
> > On Sat, Mar 26, 2016 at 7:06 AM, Thompson, David <
> dthompson2@worcester.edu>
> > wrote:
> >>
> >> On Fri, Mar 18, 2016 at 4:51 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> >> > "Thompson, David" <dthompson2@worcester.edu> skribis:
> >> >
> >> >> I noticed that 'guix environment --container --network' didn't work
> on
> >> >> an Ubuntu machine I was on, and the culprit was remounting things
> like
> >> >> /etc/resolv.conf read-only after the initial bind mount.
> >
> >
> >
> > One thing that I have run across is the following :
> >
> > $ cat /etc/resolv.conf
> > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> > resolvconf(8)
> > #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> > nameserver 127.0.1.1
> >
> > It re-writes that file every time a new network connection is made.
> >
> > $ man resolvconf
> > [...]
> > DESCRIPTION
> >        The resolvconf package comprises a simple database for  run-time
> > name‐
> >        server information and a simple framework for notifying
> applications
> > of
> >        changes in that information.  Resolvconf thus sets  itself  up  as
> > the
> >        intermediary  between  programs  that supply nameserver
> information
> > and
> >        applications that use that information.
> > [...]
> >
> > I am not at all sure if this is the cause of the issue, but I have run
> into
> > it many times before with WiFi and me trying to edit it to 8.8.8.8, so I
> > figure this is a decent time to bring it up.
>
> Interesting!  Is this on Ubuntu as well?
>
> - Dave
>