On Wed, 20 Aug 1997, Bill Studenmund wrote:

> > The problem is that it needs the dev that needs to be fsck-ed to be 
> > specified; it doesn't just assume one like it used to.  The fstab appears 
> > to be in good shape... it looks like:
> 
> [/etc/fstab]
> 
> > I'm assuming that the way it runs fsck at startup is essentially just 
> > invoking fsck -f.  At least, the way it fails is about the same...  (It 
> > says, "fsck [-dfnpy] [-b block] [-c level] [-m mode] filesystem ..." 
> > instead of running.)
> 
> Actually it's fsck -p, when it should be fsck -p /

Okay...  Where can I find that, so that I can change it?  (This is 
starting to annoy me...

	-Seth Miller