[ Frederik Schüler] > Manual fscking of these filesystems is mandatory.
This sound to me like a good argument to make -a a no-op, and not do any checking when it is specified. fsck.fstype -a is the interface used by fsck, and this make me believe it should work also for fsck.ocfs2. Would such change solve the problem with boot? I believe it is best to avoid special case handling in the generic initscripts, and thus am reluctant to try to solve it here. Of course, it could be solved in fsck, teaching it to not call 'fsck.ocfs2 -a'. I doubt the fsck developers want to handle specially the ocfs2 file system, thought. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
