OK, sometimes after power failure, Slackware will tell me on boot:

************************************************** *****
*** An error occurred during the file system check. ***
*** You will now be given a chance to log into the ***
*** system in single-user mode to fix the problem. ***
*** Running 'e2fsck -v -y <partition>' might help. ***
************************************************** *****

....and I have to manually log in as root and run that command. I
understand there are probably good reasons for making this a manual
process - I just don't know any...can someone enlighten me? From my
novice perspective, it'd be better to run this command automatically,
so that unattended machines will boot. No?

So if someone doesn't stop me with a reason not to, I was going to
modify rc.S to skip the prompt and sulogin, and just run e2fsck -v -y
itself on all the partitions. Are there pitfalls to doing this? Is
there a better way to make sure unattended machines can come back up
(other than UPS)?

Thank you,

-Sasha Borodin

Sasha Borodin wrote:

> OK, sometimes after power failure, Slackware will tell me on boot:
>
> ************************************************** *****
> *** An error occurred during the file system check. ***
> *** You will now be given a chance to log into the ***
> *** system in single-user mode to fix the problem. ***
> *** Running 'e2fsck -v -y <partition>' might help. ***
> ************************************************** *****
>
> ...and I have to manually log in as root and run that command. I
> understand there are probably good reasons for making this a manual
> process - I just don't know any...can someone enlighten me? From my
> novice perspective, it'd be better to run this command automatically,
> so that unattended machines will boot. No?
>
> So if someone doesn't stop me with a reason not to, I was going to
> modify rc.S to skip the prompt and sulogin, and just run e2fsck -v -y
> itself on all the partitions. Are there pitfalls to doing this? Is
> there a better way to make sure unattended machines can come back up
> (other than UPS)?
>
> Thank you,
>
> -Sasha Borodin

This is found in /etc/rc.d/rc.S script. I suggest you could try putting
that command in there before "sulogin" command as part of the script, and
see if it would work. If it won't (i.e. won't run in the script before
sulogin) it will give an error, but you should still get your login and be
able to log in as root and run the command yourself.

--
Mr. Cole's Axiom:
The sum of the intelligence on the planet is a constant; the
population is growing.

Thanks for the suggestion. What I'm trying to figure out is if
anyone's tried this before. And if not, why? Is there a reason not
to run e2fsck "forcibly" on all partitions *automatically*, without
human intervention?

Thanks,

-Sasha Borodin

NeoSadist <neosad1st@charter.net> wrote in message news:>
> This is found in /etc/rc.d/rc.S script. I suggest you could try putting
> that command in there before "sulogin" command as part of the script, and
> see if it would work. If it won't (i.e. won't run in the script before
> sulogin) it will give an error, but you should still get your login and be
> able to log in as root and run the command yourself.