From: Alexander Viro viro@math.psu.edu
Subject: [9fans] Plan 9 future (Was: Re: Are the Infernospaces gone?)
Date: Mon, 8 May 2000 16:35:00 -0400 [thread overview]
Message-ID: <20000508203500.HUsr1LJCZlIqC4MATUfd9Am2MvVaOMQEG1R0LQiKGPo@z> (raw)
On Tue, 9 May 2000, Roman V. Shaposhnick wrote:
> On Mon, May 08, 2000 at 12:12:52PM -0400, Russ Cox wrote:
> > Many of the tools stand without the per-process
> > namespaces. That's why I think the ported libraries
> > would be useful. It's not clear to me how to implement
> > something like 9spaces usefully. As Dave mentioned,
> > Dong has built 9P support into FreeBSD, and now
> > we know someone is doing one for Linux too. But there's
> > still no per-process namespace. I started something
>
> We hope to get the similar thing in Linux. A lot of work
> has been done at a kernel level already, but the real problem
> is userspace. Thus, I guess that from 2.4 Linux will be an
> ideal environment to do that kind of porting.
Heh ;-) Three sets of patches before we get proper namespaces. Kernel
_does_ support everything needed right now, I'll just have to merge
union-mount patch and add a new flag to clone(2) (==rfork()). BTW, the
last set fed into the tree (hopefully to be there in pre7-7) includes the
equivalent of bind(2) and support for disjoint mount trees.
So you will get namespaces - I didn't look too deep into the porting that
work to 4.4, but for Linux the thing is coming. And it's cleaner than
1995 vintage Plan 9 one - e.g. our design handles ".." for any mount
graphs in the right way, ditto for pwd, etc. I'ld love to compare the
thing with current Plan 9 stuff - hopefully during the USENIX. So if
anybody is interested...
next reply other threads:[~2000-05-08 20:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-08 20:35 Alexander [this message]
[not found] <200005052042.QAA06869@er7.rutgers.edu>
2000-06-12 10:09 ` Tom E Arnold
-- strict thread matches above, loose matches on Subject: below --
2000-05-10 12:22 rob
2000-05-10 10:17 Lucio
2000-05-10 9:49 Lucio
2000-05-10 8:51 Noel
2000-05-10 8:51 Douglas
2000-05-09 17:53 Alexander
2000-05-09 17:14 Alexander
2000-05-09 17:07 forsyth
2000-05-09 17:05 rob
2000-05-09 16:55 Russ
2000-05-09 16:31 Alexander
2000-05-09 16:18 Alexander
2000-05-09 16:15 rob
2000-05-09 16:10 dhog
2000-05-09 14:46 Alexander
2000-05-09 11:48 forsyth
2000-05-09 8:18 Douglas
2000-05-09 8:18 Ishwar
2000-05-08 20:11 Roman
2000-05-08 16:12 Russ
2000-05-08 13:45 Lucio
2000-05-08 13:05 Bengt
2000-05-08 12:48 Lucio
2000-05-08 12:09 Leo
2000-05-08 6:56 Bengt
2000-05-08 6:28 okamoto
2000-05-08 4:34 Russ
2000-05-08 4:33 rob
2000-05-08 3:55 okamoto
2000-05-06 12:47 Steve
2000-05-06 7:28 Lucio
2000-05-06 7:04 Lucio
2000-05-05 22:00 G.David
2000-05-05 20:53 Scott
2000-05-05 20:42 Anthony
2000-05-05 17:08 Lucio
2000-05-05 16:38 Lucio
2000-05-05 15:32 forsyth
2000-05-05 14:45 Lucio
2000-05-05 14:44 jmk
2000-05-05 14:42 Lucio
2000-05-05 14:20 Lucio
2000-05-05 14:14 Lucio
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=20000508203500.HUsr1LJCZlIqC4MATUfd9Am2MvVaOMQEG1R0LQiKGPo@z \
--to=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).