Loadlin fails where lilo succeeds.
initrd was made while the deb for the self prepared
kernel-image-2.6.0-test2 package was installed. Lilo boots fine. Yet
when launching loadlin, and activating an identical kernel image and
initrd like the ones that are used with lilo, I get:
[ looks like the expected boot process ]
mknod: when creating special files, major and minor device numbers
must be specified.
Try `mknod --help' for more information.
Fatal: Module ext3 not found.
mount: fs type ext3 not supported by kernel.
mount: special device /dev2/root2 does not exist
mount: special device /dev2/root2 does not exist
mount: you must specify the file system type
pivot_root: No such file or directory
/sbin/init: 196: cannot open dev/console. No such file
Kernel panic: Attempted to kill init!
Why when booting with lilo the fact that the ext3 module is not there
causes it to continue with ext2 while this is not the case for loadlin?
What component is mainly responsible: loadlin, mkinitrd or the kernel?
Both lilo and loadlin can boot with 2.4.21 and an initrd that was made
for that kernel.
The loadlin version is 1.6c-0.3.
--
Shaul Karl, shaulk @ actcom . net . il
Reply to: