Edward, please drive this to a solution. Thanks Jeff. Hans
Jeff Mahoney wrote: > Edward Shishkin wrote: > > >Russell Coker wrote: > > >>On Monday 18 July 2005 06:01, Edward Shishkin <[EMAIL PROTECTED]> > wrote: > >> > >> > >>>FC4-test3 (and perhaps FC4) installs its own version of grub which > seems > >>>to interact incorrectly with reiserfs. The problem is that reiserfs.ko > >>>module located on reiserfs partition can not be loaded. > >>> > >> > >>Firstly there is no situation in which reiserfs.ko will be loaded from > >>a reiserfs partition. > >> > >> > >Hmmm... actually this is a default situation when installing with root > >on reiserfs.. > > >>If the root file system is reiserfs then reiserfs.ko will (or at least > >>should) be included in the initrd. > > >Right, but initrd is in /boot which is not something separate: it is > on the > >same reiserfs root partition.. > > > The situation you're describing is one that is well tested by now. > > If the root filesystem is reiserfs, and /boot is a part of it, > reiserfs.ko MUST be in the initrd. Otherwise, there is a chicken/egg > problem and the system will not boot. > > The initrd being on a reiserfs filesystem is fine since grub doesn't use > any kernel services when it's executing. Grub loads the kernel and the > initrd itself before transferring control to the kernel and uses no > kernel services to do so. Grub has its own filesystem reading code which > gets pointed to during installation. > > So, if there is truly a problem with this, I'd look at Fedora's mkinitrd. > > -Jeff > > > -- > Jeff Mahoney > SuSE Labs
