Ok tup34, you got me interested, considering I never looked at the man pages for cdrecord, I prefer to use the k3b GUI interface myself...
And...
Your right, it is very confusing for someone "not in the know" of Linux's "tinkering"
From what I have seen, and heard, first step is to find out the "dev=" part, and that is done, as it says in the man pages, by using "cdrecord -scanbus" - below is what that command gave me as output...
Code:
cuddles@Polaris:~$ cdrecord -scanbus
Cdrecord-Clone 2.01a25 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to <cdrtools@packages.debian.org>.
The original author should not be bothered with problems of this version.
Linux sg driver version: 3.1.25
Using libscg version 'schily-0.8'.
scsibus0:
0,0,0 0) 'SONY ' 'DVD-ROM DDU1611 ' 'GYS1' Removable CD-ROM
0,1,0 1) 'OPTORITE' 'CD-RW CW5201 ' '160E' Removable CD-ROM
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
scsibus1:
1,0,0 100) 'SanDisk ' 'ImageMate II ' '1.30' Removable Disk
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) *
cuddles@Polaris:~$
From this output, my CD-RW is at 0.1.0 - so my dev= would be "dev=0.1.0" - thats as far as I can figure out... Not sure, looking through the manual, how you provide a "image" file to cdrecord, but I would guess, you will want to include the command line switch for DAO - or Disk At Once - so, the best I can come up with is...
cdrecord -scanbus -=- to get the "dev" for your CD-RW device,
and then
cdrecord -dev=[scanbus output of device found in above command] ...
thats as much as I can help, I'm going back to k3b - its way easier [giggle]
Cuddles