disk inconsistency - should 'fsck' always executed with -y ?

[glenn at aoi.ultranet.com (Glenn Burkhardt)]

This question really applies to all Unix systems (I think - at least, it 
applies to SunOS, Solaris, and Linux).

Occasionally after a power failure, the disk check after boot will fail, 
dropping the system into single user mode.  The way I've always dealt with it
is to execute 'fsck -y /dev/<devname>' after the single user command prompt
comes up.

Is there some reason I shouldn't modify the boot scripts to use the '-y' option
all the time?  I've never investigated what I can do otherwise.  In any case,
for production systems that are used by non-computer types, this has been
a continuing annoyance.  I end up telling folks to type in some gobbly gook,
and the computer fixes itself.  Shouldn't the computer just always fix itself?

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).