From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: ReiserFS List <reiserfs-list@namesys.com>
Subject: [Fwd: Re: rootfs and /dev/root]
Date: Wed, 21 May 2003 14:36:04 +0200 [thread overview]
Message-ID: <3ECB72B4.1030302@gmx.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 93 bytes --]
This seems to be a possible solution for reiserfsck of root partition.
Regards,
Carl-Daniel
[-- Attachment #2: Re: rootfs and /dev/root --]
[-- Type: message/rfc822, Size: 2924 bytes --]
From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: Mark Dascher <strogian@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: rootfs and /dev/root
Date: Wed, 21 May 2003 14:29:10 +0300
Message-ID: <200305211122.h4LBMsu10591@Port.imtp.ilyichevsk.odessa.ua>
On 21 May 2003 04:14, Mark Dascher wrote:
> I'm curious about the two entries in /proc/mounts:
> rootfs and /dev/root. Although I don't have much
> experience with this, I've looked through some of the
> kernel source code (e.g. fs/namespace.c or
> init/do_mounts.c). All I can come up with (actually,
> this is pretty much what I thought before I looked at
> any code) is that rootfs is purely a kernel-generated
> filesystem. The kernel creates the /dev/root device
> there, and then mounts /dev/root at / (replacing
> rootfs).
Yes that's what happens. Guys are planning to be able to
*really* umount real (disk-based) root fs someday
and continue halt/reboot sequence using files (scripts etc)
on this virtual rootfs.
So there will be both 'early userspace' and 'late userspace' ;)
IMHO.
--
vda
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2003-05-21 12:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3ECB72B4.1030302@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=reiserfs-list@namesys.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 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.