From: Harald Dunkel <harri@afaics.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: /proc/self/mounts in chroot vs lxc
Date: Sun, 05 Feb 2012 09:43:12 +0100 [thread overview]
Message-ID: <4F2E4120.3030506@afaics.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi folks,
AFAIK /proc/mounts (-> self/mounts) is supposed to replace
/etc/mtab. Problem is: In a chroot it contains too much
(invalid) information about the parent's mount points. It is
very hard to figure out which lines are correct.
For lxc there seems to be no such problem, so I wonder if it
would be possible to extend this scheme to chroot?
I am not sure if this is a kernel or libc issue. Any helpful
comment would be highly appreciated.
Regards
Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk8uQSAACgkQUTlbRTxpHjebAACcDv8p76s834XRmt24Abyi2lei
Bg4An2zTYIvKz8uD7iYZ3f46fymZ+Guk
=pYTm
-----END PGP SIGNATURE-----
next reply other threads:[~2012-02-05 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 8:43 Harald Dunkel [this message]
2012-02-05 10:33 ` /proc/self/mounts in chroot vs lxc Michael Tokarev
2012-02-06 6:33 ` Harald Dunkel
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=4F2E4120.3030506@afaics.de \
--to=harri@afaics.de \
--cc=linux-kernel@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