Joerg Schilling wrote:
> Try to start with reading the cdrecord manual page. Your question
> is answered in there.....but if you issue a command that is only
> halfway correct you will never be able to get the full set of features from
> cdrtools. Using UNIX device names for SCSI devices is highly nonportable
> and for this reason not supported by a portable program like cdrecord.
>
> Cdrecord includes the needed features to do what you like, but do not
> asume that you will be able to force me to make nonportable and Linux
> specific interfaces a gauge for the design of a portable program.
> If you read the cdrecord man page, you know that you could
> happily call cdrecord dev=green_burner.....
Portable programs have specifics to each OS that it can be compiled on. Why
do you think some portatble programs use automake? Not ever OS defines
variables the same way or uses them the same way as others.
You are going to have to realize that accessing devices directly under
different OSes will require different code. I've read all the stuff you've
posted and it is apparent that you want all OSes to use the scsi scheme.
I don't use cdrecord much anymore since 1) I have a DVDRW and 2) I burn
DVDs mostly. It happily uses /dev/<whatever> instead of compilaining that
it's unintentional.
As far as I can see, you can use scsi ioctls on regular devices so why do
you really need to use the 3 numbers? To find the right /dev/sg and use it?
Doesn't make sense. I looked at the eject program one day. The IOCTL used
to eject a cdrom is different than solaris. Gee, I guess eject is not
portable. You should probably write a library that deals specifically with
each OS. I don't ever see something like this being portable. Especially
between a Unix environment and a Windows environment.
P.S. This is the first and will be the last time I post on this thread. I'm
not trying to flame anyone, this is mostly an enduser observation. The
native OS device usage should be used instead of something supposedly
portable.
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]