lkml.org 
[lkml]   [2003]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: initrd and 2.6.0-test8
    Date
    Dnia sob 18. października 2003 21:25, viro@parcelfarce.linux.theplanet.co.uk 
    napisał:
    > 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...
    What about situation when devfs is not mounted and even not used at all, and
    it is still not working?
    --
    Witold Kręcicki (adasi) adasi [at] culm.net
    GPG key: 7AE20871
    http://www.culm.net
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 13:58    [W:0.041 / U:29.404 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site