From owner-freebsd-current  Fri Mar  3 00:32:53 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id AAA04613 for current-outgoing; Fri, 3 Mar 1995 00:32:53 -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 AAA04607 for <current@freebsd.org>; Fri, 3 Mar 1995 00:32:52 -0800
Received: from starkhome.UUCP (root@localhost) by sbstark.cs.sunysb.edu (8.6.9/8.6.9) with UUCP id DAA14077 for current@freebsd.org; Fri, 3 Mar 1995 03:33:00 -0500
Received: by starkhome.cs.sunysb.edu (8.6.10/1.34)
	id DAA07991; Fri, 3 Mar 1995 03:32:24 -0500
Date: Fri, 3 Mar 1995 03:32:24 -0500
From: starkhome!gene@sbstark.cs.sunysb.edu (Gene Stark)
Message-Id: <199503030832.DAA07991@starkhome.cs.sunysb.edu>
To: current@FreeBSD.org
In-reply-to: "Jordan K. Hubbard"'s message of Thu, 02 Mar 1995 17:58:26 -0800
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
>
>Actually, you're wrong.  His problem WAS caused by a failure to rebuild
>config.  It was Ugen's problem that was caused by the bogus SCSI device
>references..
>
>					Jordan

I see ... you are able to divine who is using SCSI devices and who is
using IDE only, so as to apply the proper flamage to people using SCSI
who got the error messages because they didn't recompile config,
and to avoid flaming people who are using IDE only and got the error
messages because they configured a kernel without SCSI.

							- Gene