Purple Shirt wrote:
the mk_initrd from suse does work. I admit though that suse has done a pretty bad job in getting this set up easily. well its a new feature....
I set up my / as ext3 when I installed, and it worked without a hitch. It must have been pretty easy as I don't remember having any problems. ;-) I have updated aaa_base package, which has a newer mk_initrd than the install I guess and it has worked fine updating to 2.4.16, back to 2.4.10, then back again to 2.4.16
On Fri, 18 Jan 2002 21:40:14 -0500 "Rafael E. Herrera"
wrote: I created the journal in the filesystem, added jbd and ext3 modules to my initrd, downloaded the fixed mk_initrd, created the new initrd file, run lilo and, finally, at boot passed the option rootfstype=ext3. The result was a kernel panic with the root partition unable to be mounted.
Did you change fstab?
So to so called fixed mk_inintrd from SuSe doesn't work either. You have 2 choices:
Mine works fine, as modules. jbd and ext3 are in my INITRD_MODULES section in rc.config., and initrd works without a hitch.
(1) Compile jbd and ext3 into the kernel.
(2) Download Redhat's version- mkinitrd, compile and use it instead. I know it works. That was my work around when I was using modules.
Try updating aaa_base. I haven't had any ext3 problems. BTW, this is on 7.3. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris Registered Linux user 231871