Subject: Re: scsi id #'s vs. driver id's
To: Armen Babikyan <armenb@moof.ai.mit.edu>
From: Allen Briggs <briggs@puma.macbsd.com>
List: port-mac68k
Date: 09/01/1997 21:05:44
> i don't know if this question is port-mac68k specific, but why does NetBSD
> use it's own driver scheme, rather than Linux's, where the number in the
> device driver would correspond to the SCSI ID?

It's not port-mac68k specific.  You can, if you build your own kernel,
have the SCSI IDs hardwired.

The BSD method is more flexible with multiple scsi busses, though.  How
would linux number with two busses?  Or with a device that has multiple
disks on multiple luns of one target (like some old ESDI interfaces did,
I think)?

> sometimes i shut off disk ID #2 because i don't need it, but that's not
> cool with /etc/fstab, which wants to now see the SCSI ID #3 drive as
> /dev/sd2

It sounds like you might want to hardwire the scsi IDs in your kernel.
That's easy to do.  Add likes like the following to your configuration
file, reconfig, and rebuild:
sd0	at scsibus? target 0 lun ?
sd1	at scsibus? target 1 lun ?
...

-allen

-- 
              Allen Briggs - end killing - briggs@macbsd.com