From owner-freebsd-current  Thu Mar  2 17:55:19 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA23156 for current-outgoing; Thu, 2 Mar 1995 17:55:19 -0800
Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id RAA23149 for <current@freebsd.org>; Thu, 2 Mar 1995 17:55:17 -0800
Received: from starkhome.UUCP (root@localhost) by sbstark.cs.sunysb.edu (8.6.9/8.6.9) with UUCP id UAA13632 for current@freebsd.org; Thu, 2 Mar 1995 20:55:20 -0500
Received: by starkhome.cs.sunysb.edu (8.6.10/1.34)
	id UAA12649; Thu, 2 Mar 1995 20:54:28 -0500
Date: Thu, 2 Mar 1995 20:54:28 -0500
From: starkhome!gene@sbstark.cs.sunysb.edu (Gene Stark)
Message-Id: <199503030154.UAA12649@starkhome.cs.sunysb.edu>
To: current@FreeBSD.org
Cc: jkh@freefall.cdrom.com
Subject: Re: kernel auf BLUES schiefgelaufen (fwd)
Sender: current-owner@FreeBSD.org
Precedence: bulk

> Do you actually read this mailing list?  :-)  Peter Dufault warned everyone
> to rebuild config earlier today, and there was a pre-warning yesterday as
> well..  Notice to all:  Please don't run -current if you can't get mail
> from this list in a timely fashion!

As we all know by now, the problem was not caused by a failure to recompile
config, but rather a failure of the person committing the changes to
properly #ifdef the scsi references so that people who don't have SCSI
devices can still link the kernel.

So, I don't think this type of shoot-from-the hip reply was called for,
especially since you obviously didn't check into it yourself to see what
the problem really was.

							- Gene