<div dir="ltr">In Debian:<br><br>The script that does the checks is /etc/init.d/checkroot.sh<br><br>You can use the following options:<br>1. create /fastboot file, so fsck won't run at all.<br>2. change the value of rootcheck variable, so fsck won't run at all.<br>
3. change the vaule of FSCKFIX variable, so fsck will get the -y option instead of -a option. (see line 257 in the file).<br><br>Kaplan<br><br><div class="gmail_quote">On Mon, Feb 15, 2010 at 7:22 PM, Noam Rathaus <span dir="ltr"><<a href="mailto:noamr@beyondsecurity.com">noamr@beyondsecurity.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<br>
When a Debian (Linux in general as well) fails on the fschk during the<br>
boot up it will get "stuck" until root does the "fschk" on his own,<br>
and answers manually or "automatically" yes to fix the problem.<br>
<br>
Can the process of "stuck" until root password be overcomed by telling<br>
Linux, "try to fix it on your own, I accept the damage?" via some<br>
configuration change?<br>
<br>
Thanks,<br>
Noam.<br>
<br>
_______________________________________________<br>
Linux-il mailing list<br>
<a href="mailto:Linux-il@cs.huji.ac.il">Linux-il@cs.huji.ac.il</a><br>
<a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
</blockquote></div><br></div>