Cheers Nick,
Nick Rout wrote:
Just thinking on initrd's, as I only use them on one box...
The idea of initrd is that it provides a tempoary root directory with
stuff you need to complete the boot. It does this in a ram disk. I suspect
this is why it cannot find /root - because a needed filesystem module is
in the initrd. so try this (cribbed from my machine that uses initrd)
kernel /boot/vmlinuz-2.6.9-x1 root=/dev/ram0 real_root=/dev/hda9 ro acpi=off
(thats all one line)
As you can probably see that starts the kernel with the ramdisk
(/dev/ram0) as root, then later swithes to /dev/hda9 (real_root).
Give it a try.
Did just that..
Result was that kernel booted through to a root shell prompt in busybox
(quickly, i.e. no drivers etc loaded i'd expect). --Help described very
little functionality from there though.
Thanks, Rik
--
Richard Tindall, InfoHelp Services <http://www.infohelp.co.nz>, on:
Ubuntu GNU/Linux 5.04 free OS, 2.6.10-5-k7 kernel, GNOME 2.10.0 desktop