From owner-freebsd-hackers  Sun May  5 10:05:47 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA27003
          for hackers-outgoing; Sun, 5 May 1996 10:05:47 -0700 (PDT)
Received: from eac.iafrica.com (slipper101155.iafrica.com [196.7.101.155])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA26998
          for <freebsd-hackers@freebsd.org>; Sun, 5 May 1996 10:05:41 -0700 (PDT)
Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id TAA00711; Sun, 5 May 1996 19:00:32 +0200
From: Robert Nordier <rnordier@iafrica.com>
Message-Id: <199605051700.TAA00711@eac.iafrica.com>
Subject: Re: dosfsck anyone?
To: joerg_wunsch@uriah.heep.sax.de
Date: Sun, 5 May 1996 19:00:30 +0200 (SAT)
Cc: freebsd-hackers@freebsd.org, rnordier@iafrica.com
In-Reply-To: <199605051501.RAA28990@uriah.heep.sax.de> from "J Wunsch" at May 5, 96 05:01:35 pm
X-Mailer: ELM [version 2.4 PL24 ME8a]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 5 May 1996, J Wunsch wrote:
> 
> As Robert Nordier wrote:
> 
> > A preen option is a Good Thing.  'fsck' itself has code to parse
> > /etc/fstab, skipping non-ufs filesystems.  One solution would be
> > to incorporate equivalent code in 'dosfsck'.  Possibly a more
> > elegant approach (which may be what you had in mind) would be to
> > handle the /etc/fstab parsing in a generic front-end.
> 
> I rather thought of it the other way round: similar to mount(8), keep
> fsck(8) being the generic front-end that does the fstab parsing and
> dispatching.  Much like mount(8), it could have builtin knowledge
> about some file system types (a builtin ufs checker, and the wisdom
> that procfs, swap, and cd9660 don't require checking at all), while it
> will call {/usr/sbin,/sbin}/fsck_${fstype} for all other file system
> types.

OK.  For 'fsck_msdos' I'll omit the fstab parsing, and provide for
'-p' and fsck-compatible exit status.  I guess fsck-style (and
predominantly uppercase) messages would also be in order.  The Mach
'dosfsck' actually refers to 'inodes' rather than 'clusters', but
that may be more confusing than enlightening.

--
Robert Nordier