Re: cdrecord-2.01.01a21 refuses work on Linux 2.4 if non-ide-scsi DVD-ROM is present

[scdbackup@gmx.net]

Hi,

> Does a suid root binary work in case that there is
> #if LINUX_VERSION_CODE <= 0x020600

Nope. I test with a simple cdrecord -scanbus :

The binary from 9.0 stumbles over /dev/sg1 :

  /usr/bin/cdrecord-2.01.01a21-hz100-suse-9.0:
  Permission denied. Cannot open '/dev/sg1'. Cannot open SCSI driver.

The binary from 9.3 feels not entitled to react on <= 0x020600:
  EXPERIMENTAL: LINUX_VERSION_CODE = 2060B
  /usr/bin/cdrecord-2.01.01a21-hz100:
  Permission denied. Cannot open '/dev/hda'. Cannot open SCSI driver.

With #if LINUX_VERSION_CODE <= 0x02060B it is the same
as with the binary from SuSE 9.0:
  EXPERIMENTAL: LINUX_VERSION_CODE = 2060B
  Linux sg driver version: 3.5.32
  /usr/bin/cdrecord-2.01.01a21-hz100: 
  Permission denied. Cannot open '/dev/sg1'. Cannot open SCSI driver.


There is no hardware attached to /dev/sg1.
The old CD-ROM is /dev/sg0, the burners are /dev/hd[cd].
The disks are hd[ab]. No SCSI disk.

CD devices recognized by libburn:
  0  dev='/dev/sg0'  rwrwrw :  'TEAC'  'CD-ROM CD-532S'
  1  dev='/dev/hdc'  rwrwrw :  'HL-DT-ST'  'DVD-ROM GDR8162B'
  2  dev='/dev/hdd'  rwrwrw :  'LITE-ON'  'LTR-48125S'


> There are reports that this hald sometimes interrupts the burn process.

My trouble currently is that cdrecord and cdrskin do not
lock against each other on SuSE 9.3. 

On the kernel 2.4 system cdrecord aborts on collision:
  cdrecord: Device or resource busy. 
  Cannot open '/dev/sg0'. Cannot open SCSI driver.
whereas cdrskin intentionally ignores a busy drive,
states it wasn't available and then it aborts.
Whatever, they both do not spoil each others ongoing work.

cdrskin opens O_EXCL|O_NONBLOCK and this still works
on cdrskin-to-cdrskin collisions on the SuSE 9.3 system.
But with cdrecord it is out of touch.


Have a nice day :)

Thomas