From: John P. Looney (valen at domain tuatha.org)
Date: Mon 12 Aug 2002 - 17:50:11 IST
I'm getting places.
Turns out that you can't have your /boot filesystem ext3, and the
/boot/vmlinux.gz file has to be a gzipped vmlinux file (not a vmlinuz one,
which though obvious...isn't, when you've been hitting your head off a
wall for a few days).
Also, when you mkfs a filesystem that's called "/boot", as far as the
redhat /etc/fstab is concerned, it wipes that, so when you boot a rescue
CD, it doesn't mount /dev/hda1 as /boot, and doesn't inform you of this.
(so, it's dead easy to work away on /mnt/sysimage/boot thinking you are
working on /dev/hda1, and wondering why no matter what you do, nothing
Aaaaanyway. I have it booting the redhat kernel. But, the kernel isn't
loading root as /dev/hda2 - it keeps mounting /dev/hda1.
Curiously, when I go into the boot prom, an use
"set_params" I can tell it to mount /dev/hda2 as root. But then it uses
the PROM copy of the kernel (dodgy 2.2.16 kernel), which doesn't know
ext3, so wants to fsck up my disk.
rdev on the vmlinux file, before gzipping doesn't work. I assume you
can't run rdev on the gzipped version. Any other ideas on how to tell a
kernel where it's root fs is ?
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:18:16 GMT