From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] 1/2 OT: per-process mounts/namespace @ Linux
Date: Fri, 7 Sep 2007 15:45:00 -0700 [thread overview]
Message-ID: <13426df10709071545i376e9e09s2a464f88d0fffa19@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60709071426mf4a4ea2kfdb4500fe763b0a9@mail.gmail.com>
On 9/7/07, David Leimbach <leimy2k@gmail.com> wrote:
> Then you have to worry about what happens when people do things like binding
> over /etc/passwd :-)
See all my old stuff from 2.0.36
rules: you can only make a private name space in /private
and, by definition, no special inode bits -- which was a feature to
me, I was ambivalent on the .u extensions.
I think that made it impossible to fake out the usual stuff.
ron
prev parent reply other threads:[~2007-09-07 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 20:09 Enrico Weigelt
2007-09-07 20:15 ` Eric Van Hensbergen
2007-09-07 21:26 ` David Leimbach
2007-09-07 21:38 ` Charles Forsyth
2007-09-07 22:21 ` Latchesar Ionkov
2007-09-07 22:27 ` Eric Van Hensbergen
2007-09-07 22:45 ` ron minnich
2007-09-07 22:45 ` ron minnich [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=13426df10709071545i376e9e09s2a464f88d0fffa19@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).