From mboxrd@z Thu Jan 1 00:00:00 1970 From: Drew C Subject: Re: [PATCH] environment: container: Do not remount network files as read-only. Date: Sat, 26 Mar 2016 09:59:30 -0700 Message-ID: References: <87wpozldb5.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1137c0ae6597cd052ef69a50 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58329) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ajrYk-0002pp-Sz for guix-devel@gnu.org; Sat, 26 Mar 2016 12:59:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ajrYi-0003fK-JD for guix-devel@gnu.org; Sat, 26 Mar 2016 12:59:34 -0400 Received: from mail-oi0-x22b.google.com ([2607:f8b0:4003:c06::22b]:35838) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ajrYi-0003f4-DY for guix-devel@gnu.org; Sat, 26 Mar 2016 12:59:32 -0400 Received: by mail-oi0-x22b.google.com with SMTP id h6so71288167oia.2 for ; Sat, 26 Mar 2016 09:59:31 -0700 (PDT) In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: "Thompson, David" Cc: guix-devel --001a1137c0ae6597cd052ef69a50 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 wrote: > On Sat, Mar 26, 2016 at 12:29 PM, Drew C 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=C3=A8s w= rote: > >> > "Thompson, David" 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=E2=80=90 > > 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 > --001a1137c0ae6597cd052ef69a50 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It is Linux Mint 17.3, which is based on=C2=A0Ubuntu Trust= y. So, yes, as far as I know, it should be the same on a modern Ubuntu dist= ro.

http://manpages.ubuntu.com/manpages/lucid/man8/resolvconf.8.ht= ml=C2=A0

-- drewc

On Sat, Mar 26, 2016 at 9:49 AM, Tho= mpson, David <dthompson2@worcester.edu> wrote:
On Sat,= Mar 26, 2016 at 12:29 PM, Drew C <me@dre= wc.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=C3=A8s <ludo@gnu.org> wrote:
>> > "Thompson, David" <dthompson2@worcester.edu> skribis:
>> >
>> >> I noticed that 'guix environment --container --networ= k' didn't work on
>> >> an Ubuntu machine I was on, and the culprit was remountin= g things like
>> >> /etc/resolv.conf read-only after the initial bind mount.<= br> >
>
>
> 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)
> #=C2=A0 =C2=A0 =C2=A0DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WIL= L BE OVERWRITTEN
> nameserver 127.0.1.1
>
> It re-writes that file every time a new network connection is made. >
> $ man resolvconf
> [...]
> DESCRIPTION
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 The resolvconf package comprises a simple d= atabase for=C2=A0 run-time
> name=E2=80=90
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 server information and a simple framework f= or notifying applications
> of
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 changes in that information.=C2=A0 Resolvco= nf thus sets=C2=A0 itself=C2=A0 up=C2=A0 as
> the
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 intermediary=C2=A0 between=C2=A0 programs= =C2=A0 that supply nameserver information
> and
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 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!=C2=A0 Is this on Ubuntu as well?

- Dave

--001a1137c0ae6597cd052ef69a50--