Joerg Schilling wrote:
>
> To address a SCSI device, I need to know the bus/target/lun numbers and
> I know them because I did set them up when I connected the device
> to my machine.
Agreed. Now the main problem is that sg tries to translate that
to sga, sgb (or sg0, sg1 depending on actual system used). It is
left for the application program to find the match. That would be
OK if there were no moving targets, but in reality the assignment
of scsi device names depends on the order that scsi devices were found.
So, everything may eventualy depend on if the scanner was turned on
or of when the computer was rebooted.
To fix that we would like a device like /dev/sgbus0id5lun0 .
Devfs is trying to provide such things by dynamically creating
the names in the /dev/ directory. I think that any solution should
also involve a move to 32 bit dev_t. Then the bus/id/lun could be
bit fields in the minor number. With the current 8 bit minor there
is not enough flexibility.
The worst problem is actually with scsi disks. This is why Linux
has a limit of 16 partitions on a scsi disk vs. 64 on IDE.
Itai
--
Itai Nahshon
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
