From owner-cvs-sys  Sat Feb  8 13:29:22 1997
Return-Path: <owner-cvs-sys>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA00777
          for cvs-sys-outgoing; Sat, 8 Feb 1997 13:29:22 -0800 (PST)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA00603;
          Sat, 8 Feb 1997 13:25:29 -0800 (PST)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA09402; Sat, 8 Feb 1997 13:24:58 -0800 (PST)
Received: from alpo.whistle.com(207.76.205.1) by whistle.com via smap (V1.3)
	id sma009400; Sat Feb  8 13:24:48 1997
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id NAA21403; Sat, 8 Feb 1997 13:25:13 -0800 (PST)
Message-ID: <32FCEE94.2781E494@whistle.com>
Date: Sat, 08 Feb 1997 13:22:28 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Bill Paul <wpaul@freefall.freebsd.org>
CC: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org,
        cvs-sys@freefall.freebsd.org
Subject: Re: cvs commit:  src/sys/scsi scsi_base.c scsi_driver.c scsiconf.c scsiconf.h
References: <199702080342.TAA21190@freefall.freebsd.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Bill Paul wrote:
> 

>   side-effects in the changes I made. Two things are different:
> 
>   - sc_print_addr() will print 'foodev0:' (i.e. sd0:, st0:, cd0:, etc...)
>     if the device name is known. If it's not known, it'll use a longer
>     notation. This shortens error messages back to a sane length.
> 
>   - Added a small function called sc_print_init() to set the sc_printing
>     flag so that sc_print_addr() will know that we want it to print a
>     linefeed. Used this in scsi_device_attach() to restore proper carriage
>     return printing behavior which I broke.
> 
>
This still doesn't address the main complaint.
This is that the error messages used to tell you the adapter type
and do not do so any more..
this is CRUCIAL informatio that is usually left out bye newbie 
bug reports, but which we could gather from looking at the error
message.