Thanks for the complete answer :) On Mon, Feb 15, 2010 at 1:56 PM, Lior Kaplan <kaplanl...@gmail.com> wrote: > In Debian: > > The script that does the checks is /etc/init.d/checkroot.sh > > You can use the following options: > 1. create /fastboot file, so fsck won't run at all. > 2. change the value of rootcheck variable, so fsck won't run at all. > 3. change the vaule of FSCKFIX variable, so fsck will get the -y option > instead of -a option. (see line 257 in the file). > > Kaplan > > On Mon, Feb 15, 2010 at 7:22 PM, Noam Rathaus <no...@beyondsecurity.com> > wrote: >> >> Hi, >> >> When a Debian (Linux in general as well) fails on the fschk during the >> boot up it will get "stuck" until root does the "fschk" on his own, >> and answers manually or "automatically" yes to fix the problem. >> >> Can the process of "stuck" until root password be overcomed by telling >> Linux, "try to fix it on your own, I accept the damage?" via some >> configuration change? >> >> Thanks, >> Noam. >> >> _______________________________________________ >> Linux-il mailing list >> Linux-il@cs.huji.ac.il >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > >
_______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
