From: Christoph Hellwig <hch@caldera.de>
To: "Peter J. Braam" <braam@mountainviewdata.com>
Cc: Alexander Viro <viro@math.psu.edu>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ronald G. Minnich" <rminnich@lanl.gov>
Subject: Re: [PATCH][CFT] per-process namespaces for Linux
Date: Mon, 26 Feb 2001 21:23:51 +0100 [thread overview]
Message-ID: <20010226212351.A15963@caldera.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0102242253460.24312-100000@weyl.math.psu.edu> <NEBBIIJKCMJGDLNAMBCBMEDKCEAA.braam@mountainviewdata.com>
In-Reply-To: <NEBBIIJKCMJGDLNAMBCBMEDKCEAA.braam@mountainviewdata.com>; from braam@mountainviewdata.com on Mon, Feb 26, 2001 at 08:26:23AM -0800
On Mon, Feb 26, 2001 at 08:26:23AM -0800, Peter J. Braam wrote:
> - when you login, you get imounted into an environment where you have full
> priviliges (except mknod). The "/" of your environment is not a directory
> in the Unix tree.
> - in this environment the system file systems are available to you on a
> copy on write private basis.
> - any files you change get out over a network file system to a server. We
> used InterMezzo backed by a ramfs cache.
>
> When the user logs out, everything is gone, except possibly footprints in
> swap.
These changes can be used separately, can't they?
I'd really like to use them with Al's more generic namespaces concept.
Once thing that worries is that his patch want special privilegs for
creating a new namespace and I wonder if we really want that...
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-02-26 20:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 4:16 [PATCH][CFT] per-process namespaces for Linux Alexander Viro
2001-02-26 16:26 ` Peter J. Braam
2001-02-26 20:23 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-25 5:28 Rick Hohensee
2001-02-25 5:40 ` Alexander Viro
2001-02-25 10:44 Manfred Spraul
2001-02-25 16:04 ` Alexander Viro
2001-02-25 19:01 ` Sandy Harris
2001-02-25 19:13 ` Alexander Viro
2001-02-25 21:57 ` Werner Almesberger
2001-02-25 22:39 ` Alexander Viro
2001-02-25 23:51 ` Werner Almesberger
2001-02-26 0:26 ` Alexander Viro
2001-02-26 11:54 ` Marco d'Itri
2001-02-26 12:51 ` Alexander Viro
2001-02-26 16:43 ` Alexander Viro
2001-02-27 20:08 ` Alexander Viro
2001-02-28 7:03 ` Albert D. Cahalan
2001-02-28 7:14 ` Alexander Viro
2001-02-28 18:13 ` David L. Parsley
2001-02-28 18:07 ` Alexander Viro
2001-02-28 19:06 ` Ion Badulescu
2001-02-28 19:18 ` Alexander Viro
2001-02-28 20:17 ` Ion Badulescu
2001-02-28 7:51 ` Alexander Viro
2001-02-25 19:48 ` Arjan van de Ven
2001-02-27 9:50 ` David Woodhouse
2001-02-26 1:14 Andries.Brouwer
2001-02-26 1:39 ` Alexander Viro
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=20010226212351.A15963@caldera.de \
--to=hch@caldera.de \
--cc=braam@mountainviewdata.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rminnich@lanl.gov \
--cc=viro@math.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