All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sandy Harris <sandy@storm.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][CFT] per-process namespaces for Linux
Date: Sun, 25 Feb 2001 14:01:51 -0500	[thread overview]
Message-ID: <3A99569F.98C64B29@storm.ca> (raw)
In-Reply-To: <Pine.GSO.4.21.0102251048280.25245-100000@weyl.math.psu.edu>

Alexander Viro wrote:

> > Have you thought about supporting .tar.gz into ramfs? Creating custom
> > boot images would be simpler.
> 
> *uh*. It's definitely easier to do than it used to be, but I'm seriously
> sceptical about adding more cruft into the thing. ...
> 
> (I presume that you mean "unpacking tar.gz into initrd/floppy-loaded ramdisk"
> and not "adding into ramfs a loader of tarballs" - the latter is out of
> question, as far as I'm concerned;

Yes, indeed.

> such code belongs to do_mounts.c if it belongs anywhere at all)
> 
> IOW, look into init/do_mounts.c - that's the right place to do that
> stuff.

Methinks there are at least two possibilities that could do everything we
might need here without unnecessary complications.

One is just mount a ramdisk and extract a tarball into its root. Yes, this has
some problems -- how do you load tar when you haven't set up your root? -- but
I suspect they can be solved. At worst, this would involve some strictly limited
kluge to do that.

A better approach might be to find or invent a generic compressed file system.
Given that, you just build a compressed root, copy an image of it into ramdisk
and let the compressed FS driver handle it from there. I suspect such a driver
might be useful elsewhere as well. Does one exist?

  reply	other threads:[~2001-02-25 19:02 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 [this message]
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
  -- 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=3A99569F.98C64B29@storm.ca \
    --to=sandy@storm.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.