Re: cdrecord + udev
Hugo Vanwoerkom wrote:
> 1. introducing udev brought about a change in the transport layer
> identification from ATAPI:0,1,0 to ATA:1,1,0.
This is plain wrong as udev has NOTHING to do with your problem, really. You
said that you also changed kernel version and THAT is the point where it
changed.
Also, do NOT use dev=ATAPI:x:y:z or dev=ATA:x:y:z with linux-2.6, always use
dev=/dev/hd*. I know that cdrecord then prints some bogus messages but it is
well-known that the author has a strange focus on the way that Solaris
handles stuff. Not every text that cdrecord spits out has an actual meaning.
However, the dev=/dev/hd* approach is what works best.
> I found this by cdrecord
> dev=help and cdrevord -scanbus dev=ATA. The previously posted -scanbus
> w/o dev always produced the posted result.
Sure, because then it scans the busses that use the SCSI layer. Those include
real SCSI, USB, Firewire, SATA and other but NOT the IDE layer (the /dev/hd*
devices). This is intentional behaviour.
> 2. I realize that I haven't got a clue as to what cdrecord actually
> does.
Indeed.
> But thank you Joerg Schilling for the code and I heard that there
> are Debian issues.
There are issues with plain cdrecord, too, that its author does not care
about. Debian patches cdrecord, reduces some problem but not completely and
as a result, the author says that Debian has issues? Judge yourself about
him.
HS
--
Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de
oder über pgp.net
PingoS - Linux-User helfen Schulen: http://www.pingos.org
Reply to: