From: Werner Almesberger <Werner.Almesberger@epfl.ch>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][CFT] per-process namespaces for Linux
Date: Mon, 26 Feb 2001 00:51:03 +0100 [thread overview]
Message-ID: <20010226005103.V18271@almesberger.net> (raw)
In-Reply-To: <20010225225750.B19635@almesberger.net> <Pine.GSO.4.21.0102251702350.26808-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0102251702350.26808-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Sun, Feb 25, 2001 at 05:39:16PM -0500
Alexander Viro wrote:
> No. Just an overmount.
Ah, too bad. Union mounts would have been really elegant (allowing the
operation to be repeated without residues, and also allowing umounting
of the covered FS as a sanity check). But I guess there's no way to
implement them without performance penalty ...
> Is it worth emptying?
Probably not ... the only interesting case would be if you could completely
umount it.
> BTW, Werner - could you take a look at the
> prepare_namespace()/handle_initrd()?
Okay, I'll have a look.
> That's our late boot process taken into one place. I'm really not happy
> about the following:
Agreed on all three counts. Also, change_root might just die by evolution,
just like most of NFS-root-from-initrd (using change_root) died.
What we need is a migration plan. Right now, it seems that most people
still use change_root. Hopefully they read the little message I left them
in linux/Documentation/initrd.txt:
Current kernels still support it, but you should _not_ rely on its
continued availability.
So with some luck, distributors will switch to pivot_root sometime soon,
when deploying 2.4. So if we drop all the old junk in 2.5, the amount of
letter bombs should be small ;-)
> Again, current patch reproduces the behaviour of the main tree.
Since you've already done all the work ... ;-) It's good if we can make
one change at a time.
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, ICA, EPFL, CH Werner.Almesberger@epfl.ch /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
next prev parent reply other threads:[~2001-02-25 23:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 10:44 [PATCH][CFT] per-process namespaces for Linux 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2001-02-26 1:14 Andries.Brouwer
2001-02-26 1:39 ` Alexander Viro
2001-02-25 5:28 Rick Hohensee
2001-02-25 5:40 ` Alexander Viro
2001-02-25 4:16 Alexander Viro
2001-02-26 16:26 ` Peter J. Braam
2001-02-26 20:23 ` Christoph Hellwig
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=20010226005103.V18271@almesberger.net \
--to=werner.almesberger@epfl.ch \
--cc=linux-kernel@vger.kernel.org \
--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