[lkml]   [2003]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: initrd and 2.6.0-test8
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


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...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:58    [W:0.078 / U:1.868 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site