From: viro@parcelfarce.linux.theplanet.co.uk
To: Svetoslav Slavtchev <svetljo@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: initrd and 2.6.0-test8
Date: Sat, 18 Oct 2003 20:25:17 +0100 [thread overview]
Message-ID: <20031018192517.GD7665@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <22900.1066504204@www30.gmx.net>
On Sat, Oct 18, 2003 at 09:10:04PM +0200, Svetoslav Slavtchev wrote:
> me had the same problems,
> with devfs enabled
>
> could it be this (from Documentation/initrd)
>
> Note that changing the root directory does not involve unmounting it.
> the "normal" root file system is mounted. initrd data can be read
> root=/dev/ram0 (without devfs)
> root=/dev/rd/0 (with devfs)
> initrd is mounted as root, and the normal boot procedure is followed,
> with the RAM disk still mounted as root.
>
> the patch doesn't mention anything about /dev/rd/0 , but does for /dev/ram0
*Arrgh*
Presense of devfs is, indeed, the problem. /dev/rd/0 vs. /dev/ram0 is not
an issue; visibility of /dev/initrd, OTOH, is - we have /dev of rootfs
overmounted by devfs, so the thing becomes inaccessible.
OK, that's trivially fixable. We need to put the sucker outside of /dev,
that's all. Patch in a few...
next prev parent reply other threads:[~2003-10-18 19:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 19:10 initrd and 2.6.0-test8 Svetoslav Slavtchev
2003-10-18 19:25 ` viro [this message]
2003-10-18 19:33 ` Svetoslav Slavtchev
2003-10-18 20:32 ` Witold Krecicki
2003-10-18 20:43 ` viro
2003-10-18 22:25 ` Svetoslav Slavtchev
-- strict thread matches above, loose matches on Subject: below --
2003-10-18 18:02 Witold Krecicki
2003-10-18 19:41 ` Valdis.Kletnieks
2003-10-18 19:57 ` viro
2003-10-18 16:27 Walt H
2003-10-18 17:52 ` viro
2003-10-18 18:22 ` viro
2003-10-18 18:33 ` Christophe Saout
2003-10-18 13:05 Arkadiusz Miskiewicz
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=20031018192517.GD7665@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=svetljo@gmx.de \
/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