Does cdrdao work as normal user? (Response)

[Andre Robatino]

Bob Agel wrote:
> Looks like it works in FC6-T2 - here's the response:
>
> [bob at localhost ~]$ eject -t ; cdrdao blank --device /dev/cdrom
> --simulate
> Cdrdao version 1.2.1 - (C) Andreas Mueller <andreas at daneb.de>
>   SCSI interface library - (C) Joerg Schilling
>   Paranoia DAE library - (C) Monty
>
> Check http://cdrdao.sourceforge.net/drives.html#dt for current driver
> tables.
>
> Using libscg version 'schily-0.8'
>
> /dev/cdrom: LITE-ON CD-RW SOHR-5239V    Rev: 2$09
> Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)
>
> Blanking disk...
> ERROR: Cannot erase CD-RW.
> ERROR: Blanking failed.
>
> Bob
>
>
> On Wed, 2006-09-06 at 05:26 -0700, Antonio Olivares wrote:
>   
>> Sorry I have created a new thread with the same
>> heading and attached a (Response) to it.  I accidently
>> deleted the original poster's message, which was 
>>
>> from
>> https://www.redhat.com/archives/fedora-test-list/2006-September/msg00108.html
>> ==========
>>  I posted this question last week with no reply. Could
>> someone check whether cdrdao in FC6t2 works as a
>> normal user? For example, try a fake blank operation
>> by putting a CD-RW in the drive and running
>>
>> eject -t ; cdrdao blank --device /dev/cdrom --simulate
>>
>> as a normal user.  In FC5 this gives the error message
>>
>> cdrdao: Operation not permitted. Cannot send SCSI cmd
>> via ioctl
>>
>> as mentioned in
>>
>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=191684
>>
>> =====
>>
>> [olivares at localhost ~]$ eject -t ; cdrdao blank
>> --device /dev/cdrom --simulate
>> Cdrdao version 1.2.1 - (C) Andreas Mueller
>> <andreas at daneb.de>
>>   SCSI interface library - (C) Joerg Schilling
>>   Paranoia DAE library - (C) Monty
>>
>> Check http://cdrdao.sourceforge.net/drives.html#dt for
>> current driver tables.
>>
>> Using libscg version 'schily-0.8'
>>
>> /dev/cdrom: LITE-ON DVDRW LDW-451S      Rev: GSB4
>> Using driver: Generic SCSI-3/MMC - Version 2.0
>> (options 0x0000)
>>
>> Blanking disk...
>>
>> [olivares at localhost ~]$
>>
>>
>> Regards,
>>
>> Antonio 
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam?  Yahoo! Mail has the best spam protection around 
>> http://mail.yahoo.com 
>>
>>     
>
>   
  Thank you for both replies.  I'm guessing that the failure to blank in 
the second reply was due to the disc being mounted during the write 
attempt.  Like cdrecord, cdrdao requires the disc to be unmounted when 
it tries to write.  Unlike cdrecord, it doesn't close the drive door 
automatically, which is what the "eject -t" is for (the idea is to make 
sure the write command runs immediately after the door closes, before 
the automount happens).