https://qa.mandrakesoft.com/show_bug.cgi?id=2058
------- Additional Comments From [EMAIL PROTECTED] 2003-02-24 11:42 ------- Yes it does. Something like *** REBOOT LINUX *** Is this bad? It never used to do that. The things fsck fixes are normal as well. The usual things like i_blocks is whatever should be whatever. fixed. Even if this is completely normal, shouldn't rc.sysinit just reboot rather than say that fsck failed to fix the errors? ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Either rc.sysinit or fsck is causing this, but it started after I updated recently and got the new e2fsprogs. Once fsck runs successfully, rc.sysinit sees this as a failure and drops you to a shell. Is it possible that the return codes from fsck have changed and rc.sysinit needs to be updated so it knows a real failure from a success?
