From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] v9fs question
Date: Mon, 13 Jul 2009 18:47:30 -0500 [thread overview]
Message-ID: <a4e6962a0907131647v38c41b6dv31a40b659abfb9c3@mail.gmail.com> (raw)
In-Reply-To: <13426df10907131637v664635f3jb32e32c6fb3c103b@mail.gmail.com>
On Mon, Jul 13, 2009 at 6:37 PM, ron minnich<rminnich@gmail.com> wrote:
> On Mon, Jul 13, 2009 at 4:22 PM, Eric Van Hensbergen<ericvh@gmail.com> wrote:
>
>> Not sure how easy or difficult this would be inside the kernel -- the
>> central problem last time I looked at it was it was difficult to
>> unshare namespace after the fork.
>
> Well, my mount command cheated. When you ran the mount command, it did
> a fork and set CLONE_NS. You were, at that point, in a private name
> space. Yes, ugly, but it certainly ensured a private mount.
>
Sure, and 9mount could do the same thing, but it would be nice to
enforce it from the kernel somehow.
-eric
next prev parent reply other threads:[~2009-07-13 23:47 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 18:46 Tim Newsham
2009-07-11 18:50 ` Eric Van Hensbergen
2009-07-11 19:03 ` Tim Newsham
2009-07-11 19:47 ` Eric Van Hensbergen
2009-07-11 20:03 ` J.R. Mauro
2009-07-12 3:19 ` Uriel
2009-07-13 8:24 ` sqweek
2009-07-13 8:51 ` hiro
2009-07-13 14:20 ` Eric Van Hensbergen
2009-07-13 20:44 ` hiro
2009-07-13 21:45 ` hiro
2009-07-13 22:05 ` Eric Van Hensbergen
2009-07-13 22:18 ` J.R. Mauro
2009-07-13 23:16 ` ron minnich
2009-07-13 23:22 ` Eric Van Hensbergen
2009-07-13 23:37 ` ron minnich
2009-07-13 23:47 ` Eric Van Hensbergen [this message]
2009-07-13 23:41 ` J.R. Mauro
2009-07-13 23:50 ` erik quanstrom
2009-07-14 0:00 ` J.R. Mauro
2009-07-14 0:06 ` erik quanstrom
2009-07-14 0:01 ` Eric Van Hensbergen
2009-07-14 0:08 ` ron minnich
2009-07-14 0:46 ` J.R. Mauro
2009-07-14 0:42 ` J.R. Mauro
2009-07-14 0:58 ` Eric Van Hensbergen
2009-07-14 1:28 ` Latchesar Ionkov
2009-07-14 1:35 ` Devon H. O'Dell
2009-07-14 2:05 ` Tim Newsham
2009-07-14 0:42 ` Tim Newsham
2009-07-14 0:50 ` erik quanstrom
2009-07-14 0:56 ` Eric Van Hensbergen
2009-07-14 4:51 ` lucio
2009-07-14 4:29 ` lucio
2009-07-14 4:26 ` lucio
2009-07-13 22:00 ` Eric Van Hensbergen
2009-07-14 19:05 ` sqweek
2009-07-14 20:11 ` Eric Van Hensbergen
2009-07-13 14:59 ` lucio
2009-07-13 15:04 ` Eric Van Hensbergen
2009-07-13 15:08 ` Latchesar Ionkov
2009-07-13 19:51 ` Tim Newsham
2009-07-14 7:34 ` sqweek
2009-07-14 11:08 ` roger peppe
2009-07-14 11:20 ` hiro
2009-07-14 12:48 ` Eric Van Hensbergen
2009-07-14 15:45 ` ron minnich
2009-07-14 16:31 ` Tim Newsham
2009-07-14 20:21 ` roger peppe
2009-07-14 13:10 ` Eric Van Hensbergen
2009-07-14 13:23 ` erik quanstrom
2009-07-14 14:26 ` Eric Van Hensbergen
2009-07-14 14:44 ` erik quanstrom
2009-07-14 14:33 ` Latchesar Ionkov
2009-07-14 14:54 ` Eric Van Hensbergen
2009-07-14 15:01 ` erik quanstrom
2009-07-14 15:13 ` Eric Van Hensbergen
2009-07-14 15:19 ` erik quanstrom
2009-07-14 15:37 ` Eric Van Hensbergen
2009-07-14 16:12 ` erik quanstrom
2009-07-14 16:19 ` Eric Van Hensbergen
2009-07-14 15:06 ` Latchesar Ionkov
2009-07-14 15:48 ` ron minnich
2009-07-14 15:59 ` Eric Van Hensbergen
2009-07-14 14:37 ` Latchesar Ionkov
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=a4e6962a0907131647v38c41b6dv31a40b659abfb9c3@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@9fans.net \
/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).