[Debburn-devel] Minor problems with cdrkit-1.1.0

Eduard Bloch edi at gmx.de
Wed Dec 6 23:52:46 CET 2006


#include <hallo.h>
* Thomas Schmidt [Wed, Dec 06 2006, 04:27:35PM]:
> Hi,
> 
> wearing my scdbackup hat (not the cdrskin one)
> i explore wodim and genisoimage from
>   http://debburn.alioth.debian.org/cdrkit-1.1.0.tar.gz
> 
> My oldfashioned system is a vanilla SuSE 9.0 :
>   $ uname -a
>   Linux * 2.4.21-215-athlon #1 Tue Apr 27 00:53:38 UTC 2004
>   i686 athlon i386 GNU/Linux
> 
> Infamous YaST2 sysadmin tool found no cmake on its media.
> So i got one from www.cmake.org :
>   cmake-2.4.5-Linux-i386.tar.gz
> Very user friendly because i could make it work without
> becoming superuser by
>   PATH="$PATH:../cmake-2.4.5-Linux-i386/bin"
> 
> I'm unsure wether this earned me the following trouble:
> 
>   $ make
>   ...

... what happened in the beginning? Complaints about missing magic.h
maybe?

>   /home/stacker/cdrkit_dir/cdrkit-1.1.0/genisoimage/apple.c:
>     2410: error: `MAGIC_ERROR' undeclared (first use in this function)
>   ...
>   make[3]: *** [genisoimage/CMakeFiles/genisoimage.dir/apple.o] Error 1

O-Ha. Please do "make clean" and then run "make build/Makefile" and
watch the log output. Does it find magic.h? You can find various bits
(logs) from cmake actions in build/CMake* and subdirs.

If you have file-devel installed, it should find magic.h and enable
libmagic support, otherwise disable it.

> and make produced these two binaries
> 
>   -rwxr-xr-x    1 * *  603639 Dec  6 15:26 ./build/genisoimage/genisoimage
>   -rwxr-xr-x    1 * *  461213 Dec  6 15:27 ./build/wodim/wodim
> 
> (... now i plan to learn how to keep cmake from issuing
> colored texts.)

TERM=dumb make

> Next i applied wodim -scanbus to my quite unusual device file
> collection which simulates a busy (or ill behaving) drive by
> linking /dev/sg7 to /dev/sg1.
>   Error trying to open /dev/sg7 exclusively (Device or resource busy)...
>   retrying in 1 second.
>   [...]
>   Error trying to open /dev/sg7 exclusively (Device or resource busy)...
>   giving up.
>   wodim: Device or resource busy. 

Printing this message is the direct result of getting errno==EBUSY. Is
your drive mounted?

> Neither cdrecord nor cdrskin stumble over that setting.
> (cdrskin ignores busy drives, cdrecord can live with it
> even with the new automatic bus scan.)
> 
> After removing /dev/sg7,  -scanbus found my two ide-scsi burners.
>   0,0,0     0) '_NEC    ' 'DVD_RW ND-4570A ' '1.02' Removable CD-ROM
>   0,1,0     1) 'HL-DT-ST' 'DVDRAM GSA-4082B' 'A201' Removable CD-ROM

IIRC this behaviour is similar to the old cdrecord which it was forked
from plus Mandriva patches. It scanned for the scsi drives, but the old
cdrecord failed then with a stupid message while wodim does scan both
device types. I agree that this is pretty confusing, but the result of
trying to force different bus types into this limited t,b,l device
specification.

I have just seen that the current cdrecord has another workaround, it
scans for both device types and then maps the faked bus numbers to
something plus 1000. Well... I cannot say I like that workaround. But it
is better than apparently "hiding" the drives. I think we should
get that feature too, better than the current confusion and is
pretty straightforward to implement.

> Re-installing /dev/sg7 as ill link sabotages -scanbus again.
> But usage of dev=0,0,0 or dev=0,1,0 is still possible.

As said, is the drive mounted? Have you waited long enough? It tries
three times before giving up and continueing with the next drive.

> Of course i like wodim's ability to burn a CD without the
> need for being superuser. rw permission for /dev/sgN is enough.
> 
> I will now test wodim and genisoimage with my backup tool.
> Then i will try to implement a fair and suitable choice of burn
> programs within scdbackup's configuration scripts. (I.e. detect the
> set of available programs, evaluate their revision and help-text
> capabilities, choose one of them.)

Btw, what do you think about making -stream-file-name work again? That
function is, in theory, implemented, but has been disabled for some
reason. I think the reason was that the method of name insertion
violates iso9660 or something like that.

Eduard.

-- 
<addNtoX> ok, ich schenk mir jetzt einfach mal die frage ...und wann ist es
	fertig??? und schau selbst bei google nach



More information about the Debburn-devel mailing list