public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org, "Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH 2/5] nsenter: add --all meaning all namespaces and cwd and root
Date: Fri, 25 Jan 2013 17:39:24 +0100	[thread overview]
Message-ID: <20130125163924.GT4278@in.waw.pl> (raw)
In-Reply-To: <20130125150210.GL27413@x2.net.home>

On Fri, Jan 25, 2013 at 04:02:10PM +0100, Karel Zak wrote:
> On Mon, Jan 21, 2013 at 01:38:02AM -0500, Zbigniew Jędrzejewski-Szmek wrote:
> > I guess that most of the time one will want to enter all
> > namespaces, and then it is easier not to have to remember
> > all the option names.
> 
>  Not sure if this is the right argument. From my point of view it's
>  better to be explicit for such things, something like --all sounds
>  like a magical blackbox where semantic depends on features implemented
>  by kernel and nsenter(1). 
Hi,

I'm was trying to document how a user should enter a namespace
container created by systemd-nspawn. I would prefer not to have the
user type 'nsenter -t $PID -muipn', but something simpler.

What about an alternative patch, which implements --all which means:
"all namespaces supported by the kernel" (i.e. iterate over /proc/$PID/ns/*'
and enter all of them. This way the behaviour would depend only on the
kernel options, not on util-linux version.

Zbyszek

  reply	other threads:[~2013-01-25 16:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21  6:38 [PATCH 0/5] nsenter,unshare: small usability improvements Zbigniew Jędrzejewski-Szmek
2013-01-21  6:38 ` [PATCH 1/5] nsenter: allow arguments to be specified in any order Zbigniew Jędrzejewski-Szmek
2013-01-25 14:52   ` Karel Zak
2013-01-21  6:38 ` [PATCH 2/5] nsenter: add --all meaning all namespaces and cwd and root Zbigniew Jędrzejewski-Szmek
2013-01-25 15:02   ` Karel Zak
2013-01-25 16:39     ` Zbigniew Jędrzejewski-Szmek [this message]
2013-01-25 17:44       ` Eric W. Biederman
2013-01-25 17:59         ` Zbigniew Jędrzejewski-Szmek
2013-01-27 15:45         ` Ángel González
2013-01-28  2:38           ` Eric W. Biederman
2013-01-28 20:41             ` Ángel González
2013-01-21  6:38 ` [PATCH 3/5] nsenter: respect --exec no matter where it appears Zbigniew Jędrzejewski-Szmek
2013-01-25 15:02   ` Karel Zak
2013-01-25 15:07     ` Zbigniew Jędrzejewski-Szmek
2013-01-25 15:23       ` Karel Zak
2013-01-21  6:38 ` [PATCH 4/5] nsenter: rename --exec/-e to --no-fork/-F Zbigniew Jędrzejewski-Szmek
2013-01-25 15:03   ` Karel Zak
2013-01-21  6:38 ` [PATCH 5/5] unshare: add --all meaning all namespaces Zbigniew Jędrzejewski-Szmek
2013-01-25 15:04   ` Karel Zak

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=20130125163924.GT4278@in.waw.pl \
    --to=zbyszek@in.waw.pl \
    --cc=ebiederm@xmission.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /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