severe problem with cramfs fileystems in /etc/fstab

Hi all,

there's a severe problem if any cramfs filesystem (e.g. as used in the initrd) 
is listed in /etc/fstab:

- /etc/rc.d/init.d/system will try to run fsck on all filesystems, with the -a 
option.
- fsck.cramfs doesn't support this option, and will cause the rc script to 
assume the filesystem is broken.
- Hence the rc script will interrupt normal bootup, and dump the user to an 
emergency shell.

Not sure how to properly fix this, but two options come to my mind:
1) don't use the -a option for fscks at bootup (this option causes filesystems 
to be automatically repaired without questions. Note that `man fsck` says to 
use this option with caution. Otoh it says interactive repair during 
filesystem checks run in parallel is a bad idea, too.)
2) don't run fsck on cramfs filesystems at bootup. Obivously, that's 
just "going to work", but there may be other filesystems that require this 
kind of fix. As I see it, running fsck on cramfs is different from fscks 
on "normal" filesystems in two ways. cramfs is basically read-only, which 
means that if the cramfs has errors
a) either the tool used to create the cramfs image is broken,
b) or your HDD or RAM (where cramfs is stored) is failing, in which case you 
have a bigger problem than just some lost+found files...

With best regards,
	Stefan Fiedler