From owner-freebsd-current Fri Mar 20 12:27:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17729 for freebsd-current-outgoing; Fri, 20 Mar 1998 12:27:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17672 for ; Fri, 20 Mar 1998 12:26:46 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id PAA17448; Fri, 20 Mar 1998 15:25:38 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803202025.PAA17448@dyson.iquest.net> Subject: Re: CURRENT Kernel Status In-Reply-To: from root at "Mar 20, 98 02:24:20 pm" To: root@danberlin.resnet.rochester.edu (root) Date: Fri, 20 Mar 1998 15:25:38 -0500 (EST) Cc: karl@mcs.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ah yes, i received number 1 as well > Quite NOT fun. > I also got an ffs panic, but i think that's cause my system still > hasn't nomralized from fun with filesystems. > :) > Following up, just wanted to say that this latest set of bugs will leave crud on your filesystems that fsck cannot fix. So, if you get straight ffs panics, I want to hear about them. Most of the time, I'll discount them as "expected", but if there is something interesting, I really do want to know about them. I'll tell everyone to "shut-up" when I don't want to hear about them anymore :-). John dyson@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message