From owner-freebsd-current Wed Mar 25 16:16:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07314 for freebsd-current-outgoing; Wed, 25 Mar 1998 16:16:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07303 for ; Wed, 25 Mar 1998 16:16:26 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA32153; Thu, 26 Mar 1998 11:13:23 +1100 Date: Thu, 26 Mar 1998 11:13:23 +1100 From: Bruce Evans Message-Id: <199803260013.LAA32153@godzilla.zeta.org.au> To: fcurrent@jraynard.demon.co.uk, toasty@home.dragondata.com Subject: Re: Panic while in tulip code Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > This kernel is from the 14th..... >> >> Argh! Where have you been for the last two weeks?? >> >> If that's the biggest problem you're having, count yourself lucky, >> back up your system while you still have a filesystem left on >> it and pray that it'll stay up long enough for you to compile a new >> kernel. Friday 13th was an extremely unlucky day for the -current >> kernel and gave rise to floods of "Good Times Virus" lookalike mails >> on this list (except they weren't fakes). How did you manage to >> miss them? >> >> James >> > >Sorry, ignore that... The kernel was from the 12th, but I rebuilt it on the >14th. :) > >I didn't miss the whole discussion. :) Besides, it wasn't broken until the 15th (17:56:06 PST), so it wasn't broken on the 14th in most of the world. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message