cdrdao-devel

[Cdrdao-devel] little cdrdao command line bug

[Manuel C. <ll...@ja...>]

Hi all,

I have found a little bug in cdrdao:

when using this command line:

cdrdao copy --simulate --paranoia-mode 0 --device 0,0,0 --driver 
generic-mmc:0x0 --source-device 0,0,0 --source-driver generic-mmc:0x0

cdrdao will tell that the medium is not empty not appendable.

But this one: (cutting --source-device 0,0,0)

cdrdao copy --simulate --paranoia-mode 0 --device 0,0,0 --driver 
generic-mmc:0x0 --source-driver generic-mmc:0x0

will work as expected.

Cdrdao should note that if the --on-the-fly switch is not given and the 
source and target devices are the same, should not test the medium.

-- 
Manuel Clos
ll...@ja...

* Si no puedes hacerlo bien, hazlo bonito (Bill Gates)
* If you can't do it well, do it nice (Bill Gates)

Re: [Cdrdao-devel] little cdrdao command line bug

[Andreas M. <an...@da...>]

Manuel Clos wrote:
> 
> Hi all,
> 
> I have found a little bug in cdrdao:
> 
> when using this command line:
> 
> cdrdao copy --simulate --paranoia-mode 0 --device 0,0,0 --driver
> generic-mmc:0x0 --source-device 0,0,0 --source-driver generic-mmc:0x0
> 
> cdrdao will tell that the medium is not empty not appendable.
> 
> But this one: (cutting --source-device 0,0,0)
> 
> cdrdao copy --simulate --paranoia-mode 0 --device 0,0,0 --driver
> generic-mmc:0x0 --source-driver generic-mmc:0x0
> 
> will work as expected.
> 
> Cdrdao should note that if the --on-the-fly switch is not given and the
> source and target devices are the same, should not test the medium.

I thought that I've done that - strange. I'll check it.

Btw, I'll be on vacation for the next 4 days. 

Regards,
Andreas
-- 
Andreas Mueller                  Tel: +49 89 67808848
Ramsmeierstr. 1                Email: an...@da...
85579 Neubiberg, Germany