From owner-freebsd-current  Thu Jan  9 22:33:21 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id WAA22086
          for current-outgoing; Thu, 9 Jan 1997 22:33:21 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA22079
          for <current@freebsd.org>; Thu, 9 Jan 1997 22:33:18 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id XAA10388; Thu, 9 Jan 1997 23:33:11 -0700 (MST)
Date: Thu, 9 Jan 1997 23:33:11 -0700 (MST)
Message-Id: <199701100633.XAA10388@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Cc: current@freebsd.org
Subject: Re: 2.2-BETA and HP 12000e Superstore DAT changer
In-Reply-To: <199701100547.AAA27283@skynet.ctr.columbia.edu>
References: <199701100547.AAA27283@skynet.ctr.columbia.edu>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> My question is: why does scsiconf not probe for other LUNs?

Because many SCSI devices respond to all of their LUN's.  My old SCSI
tape drive (some-such device) claimed it was on all of it's LUN's, which
confused the heck out of FreeBSD to say the least.

Principle of least suprise here.  It's easier to 'enable' something that
is non-standard that may break standard installations than it is to have
'standard' hardware croaking all over the place.



Nate