public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Renzo Davoli <renzo@cs.unibo.it>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Zack Weinberg <zackw@panix.com>,
	Florian Weimer <fweimer@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] resolv/resolv.h: allow alternative resolv.conf files
Date: Thu, 17 Aug 2017 16:18:00 -0000	[thread overview]
Message-ID: <20170817161812.nirkklpfysswagt3@cs.unibo.it> (raw)
In-Reply-To: <272cb460-1ac0-91e3-0def-3c5ad3f08e25@redhat.com>

On Thu, Aug 17, 2017 at 11:20:53AM -0400, Carlos O'Donell wrote:
> Is there anything technically wrong with the overlay mount?

Yes. AFAIK it requires CAP_SYS_ADMIN to mount.  (see clone(2) or unshare(2)).

Please tell me how to mount an overlay in a user namespace, this would give
a solution to my problem (although a sub-optimal one, it is much more complex 
to use than an env var, IMHO).

thank you in advance.

	renzo

  reply	other threads:[~2017-08-17 16:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 11:50 Renzo Davoli
2017-08-17 12:41 ` Florian Weimer
2017-08-17 13:14   ` Zack Weinberg
2017-08-17 13:59     ` Renzo Davoli
2017-08-17 14:32       ` Renzo Davoli
2017-08-17 15:21         ` Carlos O'Donell
2017-08-17 16:18           ` Renzo Davoli [this message]
2017-08-17 16:25             ` Florian Weimer
2017-08-17 16:49               ` Szabolcs Nagy
2017-08-17 16:55                 ` Florian Weimer
2017-08-17 16:13         ` Florian Weimer
2017-08-18 15:08           ` Renzo Davoli
2017-08-18 16:41             ` Carlos O'Donell
2017-08-22  9:37               ` Renzo Davoli
2017-08-23  4:07                 ` Carlos O'Donell
2017-09-18 15:12 ` Florian Weimer
2017-09-18 15:27   ` Carlos O'Donell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170817161812.nirkklpfysswagt3@cs.unibo.it \
    --to=renzo@cs.unibo.it \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=zackw@panix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).