Subject: Re: scsi device configuration
To: None <monroe@teleport.com>
From: Scott L. Burson <gyro@zeta-soft.com>
List: current-users
Date: 02/02/1996 14:55:07
   Date: Thu, 1 Feb 1996 23:21:11 -0800
   From: monroe@teleport.com (Monroe Williams)
   
   When configuring a kernel, how does one assign specific scsi disk devices
   to specific scsi ID's?  My machine only has one scsi bus, and I'd rather
   not have /dev/sd2 move around depending on which drives are powered up...
   (I want to hardwire bus 0, target 0, lun 0 to /dev/sd0, target 1 to 
   /dev/sd1, etc.)

   BTW, at least on the mac68k port (which, I believe, doesn't yet run on 
   any machines with multiple scsi busses), would it make more sense to 
   configure the distributed kernel this way?  Most people seem to know what
   scsi IDs their devices have, but I've seen a lot of confusion on the list
   about the scsi id -> device node mapping system.

I second this.  If you folks want NetBSD to be used as widely as possible, it
will help if you make converting to it as easy as possible.  If users, once
they get up and running, want to turn on the dynamic assignments, they can do
that easily enough; there's just no reason to add this to the hurdles they
have to leap to get started.

Personally, I don't think it's much of a feature to have to edit /etc/fstab
every time I add or remove a disk that doesn't have the highest SCSI ID, but
de gustibus non disputandum and all that.  Those who want it can enable it;
those who don't shouldn't have to deal with it.

I would add that there should be a distributed SPARC kernel that mimics
the sun4c's 3 <-> 0 swap (bizarre though it is).

-- Scott