public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Laronde <tlaronde@polynum.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Virtual(?) kernel root
Date: Sun, 28 Oct 2001 13:40:16 +0100	[thread overview]
Message-ID: <20011028134016.B239@polynum.org> (raw)
In-Reply-To: <20011026215939.A13222@polynum.org> <200110280825.f9S8PROO004923@leija.fmi.fi>
In-Reply-To: <200110280825.f9S8PROO004923@leija.fmi.fi>; from hurtta@leija.mh.fmi.fi on Sun, Oct 28, 2001 at 10:25:27AM +0200

On Sun, Oct 28, 2001 at 10:25:27AM +0200, Kari Hurtta wrote:
> > 
> > Has an equivalent scheme being already discussed?
> 
> On linux/fs/namespace.c there is following comment: (from linux 2.4.12)
> 
> /*
>  * Absolutely minimal fake fs - only empty root directory and nothing else.
>  * In 2.5 we'll use ramfs or tmpfs, but for now it's all we need - just
>  * something to go with root vfsmount.
>  */
> <...>
> static DECLARE_FSTYPE(root_fs_type, "rootfs", rootfs_read_super, FS_NOMOUNT);
>  
> 
> But I do not think that that comment refers to equivalent scheme
> than what you are proposing.

Thanks for the tip. For the major part (don't speaking about /kbin or
something like that), I think the change would be more a way to see the
stuff than a lot of coding changes. In this case, having always and a
sole kernel root, will allow to mount all sort of fs (virtual or not),
and to allow kernel threads to refere to this unchanged root.

Cheers,
-- 
Thierry Laronde (Alceste) <tlaronde@polynum.org>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

      reply	other threads:[~2001-10-28 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-26 19:59 Virtual(?) kernel root Thierry Laronde
2001-10-28  8:25 ` Kari Hurtta
2001-10-28 12:40   ` Thierry Laronde [this message]

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=20011028134016.B239@polynum.org \
    --to=tlaronde@polynum.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox