On Sun, Nov 18, 2001 at 05:25:25PM -0500, Devon wrote:
> On Sunday 18 November 2001 04:54 pm, Kevin MacNeil wrote:
> > Hm, I didn't think of that. This is the most recent redhat 2.4.9-12
> > kernel, which ships with modular ext3 support. I only installed the
> > main rpm (-ivh) and made the lilo entries myself. Force of habit, I
> > guess. Plus I'm paranoid. Maybe I'll grab the 2.4.9-12 kernel-BOOT
> > rpm and see if that has the initrd file.
>
> Or, generate your own.
> 'man mkinitrd' should get you started. ;)
I tried it and it doesn't seem to be working. Where did I go wrong?
I made an initrd file:
mkinitrd /boot/initrd-2.4.9-12.img 2.4.9-12
I added a line to the 2.4.9-12 stanza in /etc/lilo.conf and re-ran lilo:
image=/boot/vmlinuz-2.4.9-12
label=Linux
initrd=/boot/initrd-2.4.9-12.img
read-only
root=/dev/hda6
append="hdc=ide-scsi"
I rebooted and dmesg shows that it's working (I think...):
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 317k freed
VFS: Mounted root (ext2 filesystem). <-- should this be here?
Journalled Block Device driver loaded
I powercycled the machine and it still fscked the root filesystem:
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS 2.4-0.9.11, 3 Oct 2001 on ide0(3,6), internal journal
blk: queue c0371660, I/O limit 4095Mb (mask 0xffffffff)
But it didn't fsck any of the others. This is /dev/hda1, /boot
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.11, 3 Oct 2001 on ide0(3,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
