From owner-freebsd-hackers Sun May 5 16:20:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA18376 for hackers-outgoing; Sun, 5 May 1996 16:20:47 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA18371 for ; Sun, 5 May 1996 16:20:41 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA28934 for ; Mon, 6 May 1996 01:20:34 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA00277 for freebsd-hackers@freebsd.org; Mon, 6 May 1996 01:20:34 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id AAA03038 for freebsd-hackers@freebsd.org; Mon, 6 May 1996 00:55:40 +0200 (MET DST) From: J Wunsch Message-Id: <199605052255.AAA03038@uriah.heep.sax.de> Subject: Re: dosfsck anyone? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Mon, 6 May 1996 00:55:39 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <2890.831330701@time.cdrom.com> from "Jordan K. Hubbard" at "May 5, 96 02:11:41 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard 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 > > The one thing that scares me about this whole scenario is having DOS > filesystems suddenly get checked when they weren't even looked at > before, perhaps then to run into a bug which causes DOSFS corruption > and some very unhappy user(s) who never even expected FreeBSD to take > such liberties with their DOS partitions. This would imply that fsck_msdos were inherently buggy (in the same degree as the msdosfs code is by now). fsck_* usually runs on the raw device, bypassing all file system layers, since it's not even clear whether or not the file system is mountable at all. It will potentially only bite people running -current, and hey!, they have to anticipate some brokeness anyway, and are responsible for a good backup strategy, aren't they? :-) This reminds me, dump_msdos(8)... :-) :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)