From owner-freebsd-current@FreeBSD.ORG  Tue May  6 09:16:28 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8CA2037B401
	for <current@freebsd.org>; Tue,  6 May 2003 09:16:28 -0700 (PDT)
Received: from smak.uberduper.com (12-213-188-143.client.attbi.com
	[12.213.188.143])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0DDF143FDD
	for <current@freebsd.org>; Tue,  6 May 2003 09:16:28 -0700 (PDT)
	(envelope-from james@uberduper.com)
Received: from bishop (unknown [208.33.24.5])
	by smak.uberduper.com (Postfix) with ESMTP
	id EF0D17D13A; Tue,  6 May 2003 09:16:25 -0700 (PDT)
From: James Satterfield <james@uberduper.com>
To: "M. Warner Losh" <imp@bsdimp.com>, current@freebsd.org
Date: Tue, 6 May 2003 09:28:37 -0700
User-Agent: KMail/1.5.1
References: <20030505.112625.16415226.imp@bsdimp.com>
In-Reply-To: <20030505.112625.16415226.imp@bsdimp.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305060928.37835.james@uberduper.com>
Subject: Re: Precaution!
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2003 16:16:28 -0000

Uhhhg. This explains a lot. Glad I decided to peek into the list today.
Thanks,
James.

On Monday 05 May 2003 10:26 am, M. Warner Losh wrote:
> If you booted a kernel from approximately April 15th through May 3th,
> there were a number of small, but critical, vm bugs.  This can cause
> file system corruption, and leave silent landmines for later.  It is
> recommended that if you did boot these kernels, you build a newer
> kernel, come up in single user and force an fsck on all filesystems.
> This is to prevent 'false' panics later that are a result of the
> corruption that might be dormant in them now.
>
> Warner
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"