From: Kari Hurtta <hurtta@leija.mh.fmi.fi>
To: Thierry Laronde <tlaronde@polynum.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Virtual(?) kernel root
Date: Sun, 28 Oct 2001 10:25:27 +0200 (EET) [thread overview]
Message-ID: <200110280825.f9S8PROO004923@leija.fmi.fi> (raw)
In-Reply-To: <20011026215939.A13222@polynum.org>
<...>
> The key point is in fact that there is the idea of a virtual kernel
> root, with some pseudo fs already set:
>
> /
> |
> --/dev
> |
> --/kbin
> |
> --/proc
>
> The "kernel" can be used via an interface that could be, for example, a
> simple interface for debugging purpose, or a simple interface to change
> the boot parameters.
>
> Supplementary resources can be mounted on the kernel root (what is
> called "root fs") with the difference that the kernel root virtual fs
> stays always _on top_ : non kernel root fs don't mask the only root (the
> kernel one), they just add resources to the root directory.
>
> The advantages?
>
> There is no more root problem for kernel threads, since
> kernel threads run with the reference of the inchanged kernel root, the
> common "root fs" being simply mounted or unmounted. No more "sliding
> carpet" problem.
>
> One can test or question the kernel via a simple interface for debugging
> purposes. Not mounting supplementary resources doesn't create a panic,
> but leave a bare bones kernel, giving for example the choice to the user
> to give boot parameters.
>
> The /dev (this is already the case with devfs) doesn't prevent from
> mounting the "root" ro (for example when syslog tries to access a device
> file created at run time).
>
> 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.
--
/"\ | Kari
\ / ASCII Ribbon Campaign | Hurtta
X Against HTML Mail |
/ \ |
next prev parent reply other threads:[~2001-10-28 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 19:59 Thierry Laronde
2001-10-28 8:25 ` Kari Hurtta [this message]
2001-10-28 12:40 ` Thierry Laronde
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=200110280825.f9S8PROO004923@leija.fmi.fi \
--to=hurtta@leija.mh.fmi.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=tlaronde@polynum.com \
/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
all inboxes | Powered by JetHome®