On Thu, Feb 11, 1999 at 04:57:16PM +0100, Joerg Schilling wrote:
>
> You could use a different name for the mapping file and make all applications
> use this file. I may thing about putting it into a later version of the
> SCSI transport lib. In this case, only the SCSI name mapping should be in this
> file.
Agreed. However, I don't like the necessity to have that library in any
kind of software that wants to access the SCSI bus - I would prefer a
solution where the application can directly open a given device, without the
need for a library to implement that mapping. An application which does not
need to scan the bus should not need to know about bus scanning, IDs etc..
> This will not work! Most SCSI transport implementations (specially the CAM
> standard) don't have different device nodes to access different devices.
It does work fine with the current setup on Linux. Since we are discussing
about a new SCSI access method, we should IMHO choose a method that makes it
easy for small applications to do their job without needing a big library
before even starting to send a single command.
Especiallym I would like to be able to open (eg.) /dev/cdrom, and send
special SCSI commands to that device - whatever it is. These links are
already installed by the distributions, and it would look logical to have
one method of access.
> However, you are free to write a shell/awk script to create he right entries
> for the file /etc/default/cdrecord This will be portable at least on
> any OS that supports SCSI bus scanning.
I only need this to work on Linux. If another OS uses a different method,
thats fine to me - we are not talkig about defining a SCSI layer which will
then be used by all operating systems, but we are talking about a working
solution for Linux. You will need special code for every different OS
anyway.
cu
Michael
--
In the beginning there was nothing, which exploded.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
