From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What to put in chroot mtab
Date: Fri, 1 Aug 2014 11:07:26 -0400 [thread overview]
Message-ID: <CAGfcS_khqA5ASe=YG-7=a5VE-fij_WtV29C9sWxP=0UeHyo=xg@mail.gmail.com> (raw)
In-Reply-To: <CADPrc80gjzpaRsYVss=_956m4LSsyfRyENy2d7U2Hjbprd83gQ@mail.gmail.com>
On Fri, Aug 1, 2014 at 11:00 AM, Canek Peláez Valdés <caneko@gmail.com> wrote:
> And just for completeness, systemd actually requires /etc/mtab as a
> link to /proc/self/mounts, so don't be surprised if software in the
> future in Linux just assumes that.
Part of the reason for this is namespace support. As namespaces
become more popular the concept of a global list of mounts goes away,
because every process on the system has its own view of the virtual
filesystem.
Chroots are just a very primitive form of file namespaces when you
think about it.
Rich
next prev parent reply other threads:[~2014-08-01 15:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 13:07 [gentoo-user] What to put in chroot mtab Peter Humphrey
2014-08-01 13:12 ` Peter Humphrey
2014-08-01 13:28 ` Dale
2014-08-01 20:46 ` J. Roeleveld
2014-08-01 21:31 ` Canek Peláez Valdés
2014-08-01 21:33 ` Canek Peláez Valdés
2014-08-01 21:39 ` J. Roeleveld
2014-08-01 21:44 ` Canek Peláez Valdés
2014-08-01 21:46 ` Canek Peláez Valdés
2014-08-02 0:27 ` J. Roeleveld
2014-08-02 0:21 ` J. Roeleveld
2014-08-02 10:08 ` Peter Humphrey
2014-08-01 23:39 ` Dale
2014-08-01 14:56 ` Peter Humphrey
2014-08-01 15:00 ` Canek Peláez Valdés
2014-08-01 15:07 ` Rich Freeman [this message]
2014-08-01 15:25 ` Peter Humphrey
2014-08-01 15:21 ` Peter Humphrey
2014-08-01 15:29 ` Canek Peláez Valdés
2014-08-01 16:50 ` Peter Humphrey
2014-08-02 18:28 ` Rich Freeman
2014-08-01 14:02 ` Rich Freeman
2014-08-01 19:32 ` Neil Bothwick
2014-08-01 20:40 ` J. Roeleveld
2014-08-02 10:38 ` Peter Humphrey
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='CAGfcS_khqA5ASe=YG-7=a5VE-fij_WtV29C9sWxP=0UeHyo=xg@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.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