From owner-freebsd-bugs Thu May 9 19:31:29 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA07981 for bugs-outgoing; Thu, 9 May 1996 19:31:29 -0700 (PDT) Received: from eac.iafrica.com (slipper119245.iafrica.com [196.7.119.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA07962 for ; Thu, 9 May 1996 19:31:21 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id EAA00493; Fri, 10 May 1996 04:28:55 +0200 From: Robert Nordier Message-Id: <199605100228.EAA00493@eac.iafrica.com> Subject: Re: bin/1181: fsck(8) option parsing To: asami@cs.berkeley.edu (Satoshi Asami) Date: Fri, 10 May 1996 04:28:54 +0200 (SAT) Cc: joerg_wunsch@uriah.heep.sax.de, bugs@freebsd.org In-Reply-To: <199605100106.SAA15076@sunrise.cs.berkeley.edu> from "Satoshi Asami" at May 9, 96 06:06:44 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Satoshi Asami wrote: > > * A procedural query: since submitting this, I've built up a list > * of various other 'fsck' problems (functional rather than cosmetic, > * mostly). > > Just out of curiosity, what are you pondering? If you are on -current > you may have seen my mail today on 160MB fsck, it is starting to > become a problem as we are trying to build a large disk array. Please > let me know. Yes, I just looking at -current. My initial interest in 'fsck' was mainly to make my 'fsck_msdos' code more compatible with it. (This was written without looking at 'fsck'). However, I thought I'd spend a week or two pulling 'fsck' apart because all the other similar stuff I've ever looked at has a lot of problems. And it is interesting to see how far 'fsck' can be pushed before it breaks, besides being a good way to study the code. I'm not really looking at the source _because_ I want to change it, but - from results so far - I think there'll probably be a few changes I'd like to try out anyway. -- Robert Nordier