Ok my mistake there upon thinking about it a bit more I figured when we
do the /sbin/lilo thing it already figures out where to read the kernel
from assuming you have a raid 0 or raid 1. Raid 0 is just a ext2
filesystem with a copy kept on the other partition. Raid 1 is a ext2
filesystem with the superblock info kept at the end of the filesystem.
rieserfs I guess does something simillar to raid 1.In case of Raid 0
nothing special needs to be done in case of raid 1 you have to specify
the geometry of the hard disk since LILO is not aware of the raid 1
device. I dont know about reiserfs maybe someone can throw some light on
this - it is marked as a ext2 filesystem I assume. So whatever happens
LILO can reach the kernel in all cases. The problem starts when it tries
to read the root filesystem. If your kernel is not compiled with SCSI
and/or reiserfs support into it (not as a module) then everything is
fine. If it is supported as a module the kernel needs to have the module
in memory before it can read the filesystem which is where the initrd
comes into the picture which basically preloads the necessary modules.
Well thats my share of bakwas for today hope it is correct this time and
helped someone :).
Mithun
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/linux-india-help
