On Mon, Feb 04, 2002 at 05:18:17PM +1100, Herbert Xu wrote: > On Sun, Feb 03, 2002 at 05:55:34PM -0800, Osamu Aoki wrote: > > > Because you've changed fstab which contains the root filesystem type... > mkinitrd uses fstab to find out the root file system type, which decides > what goes into the initrd image...
Thanks :) Now it is crystal clear. I also added entries for /etc/mkinitrd/modules. So modules (jbd ext3 ext2) load automatically upon boot. I still have minor issues with "ext3" set-up, namely, "fsck" and "cramfs magic". Can anyone tell me what to do. I was told that using "ext3,ext2" in /etc/fstab is better than just having "ext3" for safe back drop when booting 2.2 kernel. Made sense. But reality was strange. At least keeping it as "ext3" made cleaner boot. Below are the details of trouble with "ext3,ext2" in /etc/fstab: 1. Boot screen had fsck messafge printing out: ... fsck 1.25 (20-Sep-2001) fsck.ext3,ext2 ... complain something like command does not exist. This is not in dmesg but just on console screen. 2. dmesg contain "cramfs: wrong magic" This happens right after "Partition check:" as cramfs: wrong magic kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. change_root: old root has d_count=2 Freeing unused kernel memory: 216k freed Osamu -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://qref.sourceforge.net/quick/ +
