From owner-freebsd-current Thu Aug 8 08:41:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA14703 for current-outgoing; Thu, 8 Aug 1996 08:41:01 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA14698; Thu, 8 Aug 1996 08:40:58 -0700 (PDT) Message-Id: <199608081540.IAA14698@freefall.freebsd.org> To: "M.R.Murphy" cc: mrm@mole.mole.org, freebsd-current@FreeBSD.org, julian@whistle.com, rd@thrush.com Subject: Re: SCSI Multiple LUN support - 2.2-960801-SNAP In-reply-to: Your message of "Thu, 08 Aug 1996 07:35:38 PDT." <199608081435.HAA03855@meerkat.mole.org> Date: Thu, 08 Aug 1996 08:40:57 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >With some devices turning on LUN support in the BIOS on a 2940 >keeps the system from booting at all. Tell me what the devices are. I'm sure they are already in the table. >Sure I can disconnect the device, build the system, turn off the new >default behavior, and continue on my way. No big deal. 2.2 is a ways off. The plan is to export information about the scsi system in a generic way through userconfig before we ship. You'll be able to at least disable tagged queuing and multi-lun probing from there if not sync/async settings as well. We may even ship the installation kernel with these two options turned off by default. >However, changing the default behavior from "my multi-lun device >doesn't work, enable it" to "my system doesn't work, take it apart" >might generate some questions. Questions that are the equivalent >of "my Mach64 doesn't work, the screen goes blank, what should I >do?" This has not been the case for BSD/OS or NetBSD and neither have a way to change this at boot time as FreeBSD will. >I know that the behavior will be changed when Justin gets some time. >I'll live with it, again, no big deal. But the direction of change >is, I think, ill-considered. I've actually considered it quite a bit. Point me to some devices that show this behavior that aren't in the NetBSD quirk table and I might think otherwise. >-- >Mike Murphy mrm@Mole.ORG +1 619 598 5874 >Better is the enemy of Good -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================