From: Ronald G Minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Private Namespaces for Linux
Date: Tue, 20 Nov 2001 15:28:19 -0700 [thread overview]
Message-ID: <0111201528190E.13061@snaresland> (raw)
In-Reply-To: <0111201448570B.13061@snaresland>
On Tuesday 20 November 2001 14:48, Ronald G Minnich wrote:
>
> > To start with, namespaces had been available on 2.4 since at least
> > March. See patches on ftp.math.psu.edu/pub/viro/ - namespaces-* is that
> > + related VFS cleanups. Currently most of that is merged into the main
> > tree. Remaining stuff will go in when I'll somewhat clean the backlog on
> > other things. And it's a real thing - it isn't limited to #M
> > combinations, any fs can be used.
So for those of you, like me, who try to follow this up:
The patches:
cftp /pub/viro > ls *name*
U4-rename-S5 namespaces-a-S8-pre2
namespaces-S2.gz@ namespaces-a-S8-pre3
namespaces-a-S10-pre2 namespaces-a-S8-pre4
namespaces-a-S10-pre9 namespaces-b-S3-pre8.gz
namespaces-a-S11-pre5.gz namespaces-b-S4-pre6.gz
namespaces-a-S2.gz namespaces-c-S4-pre6.gz
namespaces-a-S4.gz namespaces-c-S5
namespaces-a-S6-pre2 namespaces-c-S5-pre6.gz
namespaces-a-S6-pre5 namespaces-d-S2.gz
namespaces-a-S7-pre3 namespaces-d-S4-pre6.gz
ncftp /pub/viro >
Hmm, now what. Given the pace of change in 2.4 kernels, I can perhaps be
forgiven for wondering how solid all this will be.
Anyway, once it's really in I'll be happy to give it a shot. Although some
folks I know who are using it aren't quite sure it fits the description of
"private name spaces"
Also, Linux-specific only. My stuff does do the libc hack on several other
OSes, including freebsd.
Just FYI.
Oh, forgot to mention: the libc interface to my stuff also supports exporting
a name space and importing it into another process -- e.g. a child. You
really need that for fork(). But I think this will work in combination with
Erik Hendrik's bproc stuff, so you can get the equivalent of cpu on a
Scyld-based cluster. I have tested exporting name spaces to other processes
on other machines, and it works fine.
Oh, one other thing: Peter Braam and I did an alternate way of doing private
name spaces a few years ago on Linux, see the pnsdev at www.sourceforge.net.
Sorry to pollute this list with a non-plan-9 discussion, however, so I won't
respond to further flames unless they're private. Some messages are not worth
responding to in public.
ron
next prev parent reply other threads:[~2001-11-20 22:28 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 21:46 [9fans] vmware Russ Cox
2001-11-19 23:59 ` [9fans] Private Namespaces for Linux Matt
2001-11-20 5:26 ` Ronald G Minnich
2001-11-20 17:28 ` Thomas Bushnell, BSG
2001-11-20 20:46 ` Ronald G Minnich
2001-11-20 21:08 ` Alexander Viro
2001-11-20 21:48 ` Ronald G Minnich
2001-11-20 22:28 ` Ronald G Minnich [this message]
2001-11-20 23:14 ` Alexander Viro
2001-11-20 10:22 forsyth
2001-11-20 20:49 David Gordon Hogan
2001-11-20 20:57 ` Ronald G Minnich
2001-11-21 5:59 ` Taj Khattra
2001-11-20 20:54 presotto
2001-11-20 21:24 David Gordon Hogan
2001-11-20 21:49 ` Ronald G Minnich
2001-11-20 22:05 erik quanstrom
2001-11-20 22:08 David Gordon Hogan
2001-11-20 23:40 ` Dan Cross
2001-11-21 15:05 ` Boyd Roberts
2001-11-20 22:20 presotto
2001-11-20 22:40 David Gordon Hogan
2001-11-20 22:47 ` Ronald G Minnich
2001-11-20 23:29 ` Alexander Viro
2001-11-20 22:54 David Gordon Hogan
2001-11-20 23:17 ` Ronald G Minnich
2001-11-20 23:49 ` Matthew Hannigan
2001-11-20 23:31 ` Alexander Viro
2001-11-20 23:40 David Gordon Hogan
2001-11-20 23:45 ` Alexander Viro
2001-11-20 23:54 ` Matthew Hannigan
2001-11-21 17:24 ` Thomas Bushnell, BSG
2001-11-22 9:56 ` Thomas Bushnell, BSG
2001-11-20 23:48 forsyth
2001-11-21 0:03 David Gordon Hogan
2001-11-21 1:29 okamoto
2001-11-21 3:46 ` Ronald G Minnich
[not found] ` <Pine.LNX.4.33.0111202037460.14857-100000@snaresland.acl.la nl.gov>
2001-11-21 17:51 ` Skip Tavakkolian
2001-11-21 22:44 ` Ronald G Minnich
2001-11-21 3:02 Eric Grosse
2001-11-21 14:52 presotto
2001-11-21 20:12 ` Dan Cross
2001-11-21 20:48 ` Skip Tavakkolian
2001-11-21 22:50 ` Andrew Simmons
2001-11-25 15:23 ` david presotto
2001-11-25 4:19 ` George Michaelson
2001-11-21 16:49 forsyth
2001-11-21 20:08 erik quanstrom
2001-11-21 23:02 rob pike
2001-11-21 23:26 ` Matt
2001-11-22 0:36 rob pike
2001-11-22 0:42 rob pike
2001-11-26 5:31 David Gordon Hogan
2001-11-26 10:00 ` Thomas Bushnell, BSG
2001-11-26 10:48 ` Matt
2001-11-26 14:29 ` Ronald G Minnich
[not found] ` <Pine.LNX.4.33.0111260728070.16611-100000@snaresland.acl.la nl.gov>
2001-11-27 0:13 ` Andrew Simmons
2001-11-27 1:37 ` Ronald G Minnich
[not found] ` <Pine.LNX.4.33.0111261834400.19833-100000@snaresland.acl.la nl.gov>
2001-11-27 2:17 ` Andrew Simmons
2001-11-27 2:28 ` Boyd Roberts
2001-11-27 2:46 ` Andrew Simmons
2001-11-27 11:53 ` Ralph Corderoy
2001-11-27 2:22 ` Quinn Dunkan
2001-11-27 2:54 ` Andrew Simmons
2001-11-27 3:06 ` Boyd Roberts
2001-11-26 14:18 ` Ronald G Minnich
2001-11-26 18:26 ` Dan Cross
2001-11-26 18:27 erik quanstrom
2001-11-27 3:03 geoff
2001-11-27 3:09 Russ Cox
2001-11-27 8:13 ` Skip Tavakkolian
2001-11-27 6:43 David Gordon Hogan
2001-11-27 7:24 nigel
2001-11-27 8:49 nigel
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=0111201528190E.13061@snaresland \
--to=rminnich@lanl.gov \
--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).