On 12/18/06, Kenneth Pronovici <[EMAIL PROTECTED]> wrote:
On 12/18/06, Dmitry Rutsky <[EMAIL PROTECTED]> wrote:
> It turns out that I'd overlooked relevant sections in the documentation
> ("Linux Notes" in Chapter 4) and there is (or at least was) a way to use ATAPI
> interface.  Still it doesn't work for me, and

What happens when you execute this?

        cdrecord -scanbus dev=ATAPI

This is what I get on my development system (Debian etch, kernel
2.6.18-3-k7). when I run the various scanbus commands:

# cdrecord -scanbus dev=ATA
scsibus1:
       1,0,0   100) 'LITE-ON ' 'DVDRW SOHW-1673S' 'JS02' Removable CD-ROM
       1,1,0   101) *
       1,2,0   102) *
       1,3,0   103) *
       1,4,0   104) *
       1,5,0   105) *
       1,6,0   106) *
       1,7,0   107) *

# cdrecord -scanbus dev=ATAPI
scsibus0:
       0,0,0     0) 'LITE-ON ' 'DVDRW SOHW-1673S' 'JS02' Removable CD-ROM
       0,1,0     1) *
       0,2,0     2) *
       0,3,0     3) *
       0,4,0     4) *
       0,5,0     5) *
       0,6,0     6) *
       0,7,0     7) *

Now, previously, I would have told you that this means you should use
one of these SCSI ids:

       ATA:1,0,0
       ATAPI:0,0,0

However, wodim doesn't support "ATAPI", and says it's deprecated.

       # cdrecord -prcap dev=ATAPI:0,0,0
       Warning, the ATAPI: method is considered deprecated on modern kernels!
       Mapping device specification to dev=0,0,0 now.
       To force the old ATAPI: method, replace ATAPI: with OLDATAPI:
       cdrecord: Invalid argument.
       Cannot open SCSI driver!
       For possible targets try 'wodim -scanbus'.
       For possible transport specifiers try 'wodim dev=help'.
       For IDE/ATAPI devices configuration, see the file
README.ATAPI.setup from
       the wodim documentation.

Instead, you have to use "OLDATAPI".

I've checked, and I can successfully write a disk with either
ATA:1,0,0 or OLDATAPI:0,0,0 on my development system.   However, I/O
gets a little screwy with OLDATAPI -- the system is kind of
unresponsive -- and I'm not sure I can recommend using it.

Anyway, this suggests one change in Cedar Backup, which is to loosen
the regex around the SCSI parameter.  That's probably a good general
change so I don't need to release a new version of my software every
time a new method needs to be supported.  I've implemented it in
upstream Subversion as of revision 1014.

I'm going to dig a little further into your patch now and see what I
can do about supporting dev=/dev/cdrom and the like.

KEN

--
Kenneth J. Pronovici <[EMAIL PROTECTED]>
http://www.cedar-solutions.com/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to