From: Jim Winstead Jr. (jwinstea@fenris.claremont.edu)
Date: 03/26/93


From: jwinstea@fenris.claremont.edu (Jim Winstead Jr.)
Subject: Re: 386bsd, linux: which runs more out of the box?
Date: Fri, 26 Mar 1993 22:38:24 GMT

In article <1ouiso$cgq@agate.berkeley.edu> curtis@cs.berkeley.edu (Curtis Yarvin) writes:
   In article <JWINSTEA.93Mar25125111@fenris.claremont.edu> jwinstea@fenris.claremont.edu (Jim Winstead Jr.) writes:
>
>The main thing it uses to do the filesystem checking on bootup is
>fsutil-1.6, which has fsck and mkfs frontends that let you just do a
>"fsck /dev/hdb3" and it figures out the proper "real" fsck program to
>use by reading /etc/fstab (or it can be told via command line option).
>It also supports fsck -A to check all of the filesystems in
>/etc/fstab.

   How does it handle checking the mounted root filesystem? This is
   a problem I haven't been able to figure out. My best solution is
   just to reboot without syncing, immediately after the fix; but I
   am not sure this is reliable.

My solution (in /etc/rc) is to just check it along with everything
else, before /etc/update is running (so no syncs happen while doing
the fsck).

It would probably be best to check the root filesystem and then reboot
if (but only if) fsck reports that changes have been made. Shouldn't
be too hard to do, so I'll see what I come up with. :)

As I said before, I should be have a nice /etc/rc package together
sometime this weekend - read c.o.l.a. for the announcement of its
release.