From owner-freebsd-current Sat Jun 2 15:46:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-66.dsl.lsan03.pacbell.net [63.207.60.66]) by hub.freebsd.org (Postfix) with ESMTP id 28B2C37B43C for ; Sat, 2 Jun 2001 15:46:34 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6DAA0673A5; Sat, 2 Jun 2001 15:46:33 -0700 (PDT) Date: Sat, 2 Jun 2001 15:46:33 -0700 From: Kris Kennaway To: current@FReeBSD.org Subject: dirpref and RELENG_4 fsck Message-ID: <20010602154633.A25944@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Was it determined that the fsck corruption problems which were seen with fsck after the introduction of the dirpref changes do not affect RELENG_4? I haven't seen any MFC of changes to the RELENG_4 fsck code, and I'm kind of worried now that I've reverted my current system back to RELENG_4 :-) Kris --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7GWzIWry0BWjoQKURAjAFAKDjfAwsEsGaUMmhVpC8LpBi1TvjfQCg9zoY iV+bCUTAQ6k9T/1g2uzUP9k= =wwmv -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message