According to Herb Peyerl:
>
>an errant 'fsck -y' ate my /home a couple of weeks ago... I only ever
>recommend 'fsck -y' when I know the filesystem is hopelessly hosed and
>there's nothing I can do about it....  I don't mind typing "y<return>"
>a few times....
>

Hmmmm most mere mortals (I include myself in this) would not know what
to do if you answer "no" to fsck's kind offer to fix something - I
suspect it has something to do with fsdb but that is scary.  I suppose
you can always ^C if you get bored with typing Y though ;-)

>granted, it ate my /home due to what was later discovered to be a bad $12
>scsi cable...
>

oops :-(

-- 
===============================================================================
Brett Lymn, Computer Systems Administrator, BAE SYSTEMS
===============================================================================