From: Harald Dunkel <harri@afaics.de>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: /proc/self/mounts in chroot vs lxc
Date: Mon, 06 Feb 2012 07:33:28 +0100 [thread overview]
Message-ID: <4F2F7438.8040600@afaics.de> (raw)
In-Reply-To: <4F2E5B08.4010200@msgid.tls.msk.ru>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/05/12 11:33, Michael Tokarev wrote:
>
> But plain chroot does not create new namespace, the process inherits parent namespace, so there is no way to clean in up cleanly.
>
If I do a chroot to /mnt, then there is no "/mnt" in /proc/self/mounts
within this environment. Instead I see yet another entry for '/'.
This certainly looks like something private.
Maybe it would be easier for everybody if /proc/mounts (without "/self")
could always show the "real" mount points at the top level? A bind mount
of /abc to /mnt/abc would appear as /mnt/abc in /proc/mounts at all levels.
I could live with that.
Regards
Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk8vdDQACgkQUTlbRTxpHjcQOgCfXwKqVu7mAFTDctvcs1YAMQCq
FIsAn2UHiL+TncraqQffzdecN0eMadJy
=huO6
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-02-06 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 8:43 /proc/self/mounts in chroot vs lxc Harald Dunkel
2012-02-05 10:33 ` Michael Tokarev
2012-02-06 6:33 ` Harald Dunkel [this message]
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=4F2F7438.8040600@afaics.de \
--to=harri@afaics.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.