Results: NOTE: Using "probe' and "dep' in the mkinitrd, the compressed image is under 1 meg. Using 'most' or simply defaulting, one will get >3 meg. jdb, ext3 and ext2 are in the modules file or appended to 'probe' line. 1. The cramf image file is detected and loaded without complaint. The "corrected" error message is "bogus logical sector size 0", not "block size 0" as previous posted. Panic. 2. The mkext2fs image file is loaded but the loader now complains of an unrecognized/unsupported? compression type. Instead of a panic, this time it simply continues with the ext3 mounted as ext2 warning and proceeds. 3. The initrd memory is released in both cases. 4. I still have read-only in lilo. Does this make a difference? (Easy enough to try.) _______________________________________________ Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
