From owner-freebsd-current  Thu Dec  3 12:08:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA15583
          for freebsd-current-outgoing; Thu, 3 Dec 1998 12:08:31 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from knecht.Sendmail.ORG (knecht.sendmail.org [209.31.233.160])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15576
          for <current@freebsd.org>; Thu, 3 Dec 1998 12:08:28 -0800 (PST)
          (envelope-from mckusick@flamingo.McKusick.COM)
Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [209.31.233.178])
	by knecht.Sendmail.ORG (8.9.2.Alpha2/8.9.2.Alpha2) with ESMTP id MAA23931;
	Thu, 3 Dec 1998 12:08:02 -0800 (PST)
Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1])
	by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id KAA26095;
	Thu, 3 Dec 1998 10:47:08 -0800 (PST)
Message-Id: <199812031847.KAA26095@flamingo.McKusick.COM>
To: Julian Elischer <julian@whistle.com>
Subject: Re: FreeBSD fsck updated 
cc: current@FreeBSD.ORG, Don Lewis <Don.Lewis@tsc.tdk.com>
In-reply-to: Your message of "Wed, 02 Dec 1998 20:18:45 PST."
             <36661125.31DFF4F5@whistle.com> 
Date: Thu, 03 Dec 1998 10:47:07 -0800
From: Kirk McKusick <mckusick@McKusick.COM>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	Date: Wed, 02 Dec 1998 20:18:45 -0800
	From: Julian Elischer <julian@whistle.com>
	Organization: Whistle Communications
	To: current@freebsd.org
	CC: Kirk McKusick <mckusick@McKusick.COM>,
	    Don Lewis <Don.Lewis@tsc.tdk.com>
	Subject: FreeBSD fsck updated
	References: <199811230603.WAA02649@salsa.gv.tsc.tdk.com>

	I have checked in kirk's newest fsck (well, a week or so old)

	This understands soft updates a bit better, and has some improved
	checks for orrupted filesystems and  a few fixes..
	We have also incorporated soem FreeBSD fixes in kirk's sources.

	What I have left are a few small patches (attached)
	that I'm not sure about. Two appear to be fro support for
	symlinks-in-inode denoted by a 0 block count. (I'm not sure about the
	correctness of them) (when was it done that way? 386BSD?)

	one is some extra pronouncements when some bits are found unset.

	whether we merge these old freebsd bits into the current new
	version is more a political matter..

	What does everyone think? I now kirk doesn't like the 
	noisy messages about the clean and modified bits..

	julian

I don't care one way or the other about the symlink compatibility.
If there are folks still running that way, then that argues to keep
it. On the other hand, if they are upgrading to 3.0, then it may be
time for them to fix any remaining old-style links in their filesystem.

I have commented already on my dislike of the noisy info about clean
and modify bits. but here too, I do not feel strongly enough to make
a big case out of it.

	Kirk

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message