On Fri, 7 Feb 2003, Daniel R. Broemmelsiek wrote: > On Friday 07 February 2003 04:24 pm, Stew Benedict wrote: > > On Fri, 7 Feb 2003, Daniel R. Broemmelsiek wrote: > > > The kernel keeps mounting my ext3 file system as an ext2 file system on > > > this Wallstreet. Why? Is there a particular kernel argument to pass > > > from BootX? > > > > > > Dan > > > > Did you use the ext3 initrd? (BootX folder) > > > > Stew Benedict > > When? To run the installer I had to use vmlinux and all.gz during which I > just used existing partitions. Any other combination I tried went into > kernel panic. Install went fine so at reboot I point BootX to the > vmlinuz-2.4.20-2mdk kernel and my partition /dev/hda10 because that's where > it's going to find the loadable modules in /lib/modules/2.4.20-2mdk/. So I'm > curious, when and where does the kernel want to see > initrd-2.4.20-2mdk.img-ext3? > > By the way, kmail composer is doing funky black screen flashes while I'm > writing this. The first annoying thing I've found. >
Any module need to access "/" needs to be loaded by an initrd. Folks using bootX to load linux have this extra grief to deal with. Since you are using ext3 on "/" and it's modular, you need the initrd I created in the BootX folder to be able to access and mount that partition as ext3. Same would apply for scsi or other journalled filesystems. For the final, I'll try to have initrd's for all the journalled filesystems in that folder. Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3 IRC: irc.freenode.net #cooker-ppc Archives: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppc&r=1&w=2
