http://qa.mandrakesoft.com/show_bug.cgi?id=5354
------- Additional Comments From [EMAIL PROTECTED] 2003-07-09 19:26 ------- These versions of rc.sysinit correctly handle fsck return codes, as well, as correctly handling interrupted powerfail shutdowns. They provide a much more modular rc.sysinit so that user promting is more unifrom without requiring repeated code. Does this qualify me to be added to the list of contributors? :) I have marked each section where I have made changes very clearly, along w/ the date and any additional comments that might be helpful. It might be useful to move some of the functions in rc.sysinit into the functions file in /etc/init.d/functions - at least the AskForKey function. Shamim Islam -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- 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: rc.sysinit when checking for filesystem integriry fails miserably on headless machines even when the PROMPT value is set to "no". Any error unexpected return value in the root file system demands user input. Also, the return code from fsck is not interpreted correctly - fsck returns a bitfield - rc.sysinit instead compares the error level as if it were a regular integer. There is much duplicated script code for handling fsck issues. rc.sysinit does not handle an interrupted powerfail shut down.
