On Tuesday 19 July 2005 01:59, Jeff Mahoney <[EMAIL PROTECTED]> wrote: > >> 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.
This works in all my tests. The reiserfs.ko module is apparently in the initrd. Also if the original bug concerned a lack of reiserfs.ko in the initrd then re-running GRUB would not fix things. I can't reproduce the bug, it just works for me. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
