>> >>>Cdrecord is a program that needs to be able to send any SCSI command as
>> >>>it needs to be able to add new vendor unique commands for new drive/feature
>> >>>support.
>> >>
>> >>Right, but evidently it does not need the kernel to invent numbering.
>> >>dev=/dev/hdc works today.
>> >
>> > Maybe, I will need to enforce to use official libscg device names in future....
>>
>> To burden users with yet another naming policy?
>
>Well, I am open to have an unbiased discussion that may have any result but
>the parties should allow each other to convince by arguments.
>
The user should use what the OS uses. Cdrecord, or libscg, respectively,
can invent any numbers it wants. IOW, "we" (read: I) would like to see
cdrecord -dev=/dev/hdc on Linux
I am not sure if I understood your other mail on the cdrecord ML, but if
the proper syntax would be
cdrecord -dev=/dev/hdc:@
then
/dev/hdc
could just be transparently turned into
/dev/hdc:@
somewhere within the getopt part.
for other OS:
cdrecord -dev=/dev/acd0 on FreeBSD
cdrecord -dev=E: on Win32
cdrecord -dev=\\cdrom0 if someone really wants for Win32
cdrecord -dev=/dev/c0t0s0d0 on Solaris
(Don't shoot me. I unfortunately have to make a guess, since I have
not done yet any cdrecord'ing[1] on OS other than Linux.)
[1] Well with Nero, but that's not cdrecord, as in "cdrecord'ing". :)
Jan Engelhardt
--
-
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/
- Follow-Ups:
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- References:
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Kyle Moffett <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Matthias Andree <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Vojtech Pavlik <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: James Courtier-Dutton <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Jan Engelhardt <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Matthias Andree <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Jeff Garzik <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- Prev by Date: Re: CD writing in future Linux (stirring up a hornets' nest)
- Next by Date: Re: [PATCH] serial: Add spin_lock_init() in 8250 early_serial_setup() to init port.lock
- Previous by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
- Next by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
- Index(es):
 |