In article <20021206045426.GA22017@ursine>, Paul Johnson wrote: > > Wait, are you trying to boot a kernel that doesn't have ext3 compiled > in on a system whose /etc/fstab specifies the / partition as being > ext3?
Nope, ext2/ext3 have been included in the vmlinuz-image all along. I'll throw in another question here: from /etc/fstab: /dev/hdc6 / ext2 errors=remount-ro 0 1 from dmesg: kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. ... EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,6), internal journal I know I initially created / as an ext2 partition, and I can't recall having converted it to ext3 (though I could be wrong, I've certainly thought about it, I just can't recall having actually done it yet), I also just tried adriot3:~# mount -v -t ext3 -o remount /dev/hdc6 / /dev/hdc6 on / type ext3 (rw) adriot3:~# mount /dev/hdc6 on / type ext2 (rw) So why the mount as EXT3 while booting? Anyway, I've now got 2.4.20, plus the patches I wanted, up and running fine, and hopefully this won't be an issue again. It was probably some silly mistake on my part. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
