Nico van Eikema Hommes wrote:
> 
>    Hi All,
> 
> Once again, this stupid problem: fsck -p not working.
> 
> >>>>> Automatic boot in progress: starting file system checks.
> >>>>> Usage: fsck [-dfnpy] [-b block] [-c level] [-m mode] filesystem ...
> >>>>> Unknown error; help!
> >>>>> Enter pathname of shell or RETURN for sh:
> >>>even if there is a bug in the rc script (i haven't checked), running "fsck"
> >>>in single-user complains about wanting arguments...and it shouldn't...
> 
> Right. It definitely should not, but it did for quite some time. However,
> I noticed today, after setting up a 1.3alpha installation on a ZIP disk
> for testing, that it apparently has disappeared. From /etc/rc:
> 
> 	echo "Automatic boot in progress: starting file system checks."
> 	fsck -p
> 
> and that simply did what it should: check the root filesystem according to
> /etc/fstab. Interestingly, however, Armen still had the problem:
> 
> >I didn't upgrade anything. I did a full install of all the -current
> >tarballs, including etc.
> 
> Anyone know about a discrepancy here between 1.3alpha and -current (apart
> from the usual -current changing daily, etc.)?

Unless you are a developer, there is _no_ difference between 1.3 alpha and
-current (well, maybe a few patches between the latest snapshot that Steve
has put up and what's in the sup tree).  Currently, sup is following the
1.3_ALPHA branch.  I don't believe there have been any changes to fsck
which would cause this.  It seems to me that maybe some binary is not
getting properly updated for some reason...

Later.

-- 
Colin Wood                                 cwood@ichips.intel.com
Component Design Engineer - MD6                 Intel Corporation
-----------------------------------------------------------------
I speak only on my own behalf, not for my employer.