Date: Sun, 5 May 1996 19:00:30 +0200 (SAT) From: Robert Nordier <rnordier@iafrica.com> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-hackers@freebsd.org, rnordier@iafrica.com Subject: Re: dosfsck anyone? Message-ID: <199605051700.TAA00711@eac.iafrica.com> In-Reply-To: <199605051501.RAA28990@uriah.heep.sax.de> from "J Wunsch" at May 5, 96 05:01:35 pm
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605051700.TAA00711>