Date: Fri, 10 May 1996 04:28:54 +0200 (SAT) From: Robert Nordier <rnordier@iafrica.com> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: joerg_wunsch@uriah.heep.sax.de, bugs@freebsd.org Subject: Re: bin/1181: fsck(8) option parsing Message-ID: <199605100228.EAA00493@eac.iafrica.com> In-Reply-To: <199605100106.SAA15076@sunrise.cs.berkeley.edu> from "Satoshi Asami" at May 9, 96 06:06:44 pm
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605100228.EAA00493>