Hi, Theodore Ts'o wrote:
on my system, when fsck fails due to some "unexpected inconsistency", the boot process does not halt. It appears as if $CONSOLE were set to some invalid value, and sulogin thus fails.
If $CONSOLE is set to an incorrect problem, this is probably an initscripts problem. It's certainly not an e2fsck or fsck problem....
It is to a certain extent. If $CONSOLE is incorrect, the user will see a message that he is supposed to log in now and manually fix the problem, but the boot process continues normally, mounting the inconsistent filesystems read/write as the next step.
I'd have no problem with the boot process stopping entirely if sulogin fails, probably with an explanatory message.
Simon
signature.asc
Description: OpenPGP digital signature
