From owner-freebsd-hackers Sun May 5 06:40:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA16776 for hackers-outgoing; Sun, 5 May 1996 06:40:40 -0700 (PDT) Received: from eac.iafrica.com (h196-7-192-140.iafrica.com [196.7.192.140]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA16770 for ; Sun, 5 May 1996 06:40:34 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id PAA00347; Sun, 5 May 1996 15:35:18 +0200 From: Robert Nordier Message-Id: <199605051335.PAA00347@eac.iafrica.com> Subject: Re: dosfsck anyone? To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 5 May 1996 15:35:17 +0200 (SAT) Cc: freebsd-hackers@freebsd.org, rnordier@iafrica.com In-Reply-To: <199605050948.LAA27697@uriah.heep.sax.de> from "J Wunsch" at May 5, 96 11:48:26 am 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: > > > I'm currently in the process of finishing off a BSD implementation > > of 'dosfsck', an 'fsck'-style utility for checking and repairing > > DOS FAT (and later VFAT) filesystems. > > > (Example 1) > > > > Directory '/junk' is cross-linked on cluster 4. Truncate [yn]? y > > . . . . . > > Warning: directory '/keep' was also cross-linked on cluster 4. > > I think i would go with this. Anyway, _any_ decent dosfsck might be a > nice deal. That's my preference also. > What about making `fsck' generic in the same way as `mount' is, btw? > This way, an `fsck -p' would also be able to call fsck_msdos if > there's a file system of type msdos in /etc/fstab. 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. The manpage doesn't specify 'fsck -p' as taking filesystem arguments, but it appears to accept them OK. It would then be only optional to modify 'fsck', and the front-end would be available to dispatch all 'fsck'-type utilities. -- Robert Nordier