From: Lee Causier <LeeCausier@GameBox.net>
To: Adrian Etchevarne <aetcheva@it.itba.edu.ar>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Private namespaces
Date: 16 Apr 2003 14:40:15 +0100 [thread overview]
Message-ID: <1050500415.4929.3.camel@kurta> (raw)
In-Reply-To: <1052141040.355.12.camel@labunix>
http://www.win.tue.nl/~aeb/linux/lk/lk-6.html
Take a look at 6.3.3 "Per-process namespaces"
[-- snip --]
"BUGS: The program mount does not know about this feature yet, so
updates /etc/mtab. Reality is visible in /proc/mounts. Some kernel
versions have a bug that would cause the new process to have a strange
working directory. Probably that is avoided if this is started with a
working directory / or so - not in some mounted filesystem."
I found symlinking /etc/mtab to /proc/self/mounts (or /proc/mounts,
mhich is a symlink to /proc/self/mounts) solved the mount bug.
HTH
Regards,
Lee Edward Causier.
On Mon, 2003-05-05 at 14:23, Adrian Etchevarne wrote:
> Hello,
> I've been looking for instructions to use private namespaces in Linux,
> without results. Can anyone tell where is the documentation about it?
> (I'm not refering to chroot(), but to /proc/<pid>/mounts). Or the proper
> files in the kernel sources?
>
> Thanks,
> Adrian.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-04-16 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 13:23 Private namespaces Adrian Etchevarne
2003-04-16 13:23 ` Andries Brouwer
2003-04-19 14:52 ` Florin Iucha
2003-04-19 16:21 ` Andries Brouwer
2003-04-19 21:35 ` Andrew Morton
2003-04-16 13:40 ` Lee Causier [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-19 22:18 Andries.Brouwer
2003-04-19 22:22 ` Andrew Morton
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=1050500415.4929.3.camel@kurta \
--to=leecausier@gamebox.net \
--cc=aetcheva@it.itba.edu.ar \
--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