[Debburn-devel] wodim -tao and wodim -msinfo doesn't work on a DVD

[Thomas Schmitt]

Hi,

i do not understand all details of burn.py yet. Lack of python knowledge. :))

But i'd say that "xorriso -as mkisofs" could take over the job
of genisoimage and "xorriso -as cdrecord" or "cdrskin" could do
the job of cdrecord in there.


Is this an eject/load cycle ?
  cdrecord -eject dev=... > /dev/null 2>&1 && cdrecord -toc dev=... > /dev/null 2>&1
Suffering from the block device driver's inconsciousness, eh ?
I would rather use program "eject" here. It is nearer to the driver
which you want to give a kick. E.g.:
  eject /dev/... && sleep 2 && eject -t /dev/...

The burn programs operate the driveis on Linux via the generic scsi driver.
I assume eject uses the cdrom driver.


Creation of checksums, verifying them, and listing could be done by
xorriso on the fly.
Creation:
  xorriso -as mkisofs --for_backup ...your.genisoimage.options...
Verification of most recent session
  xorriso -for_backup -indev /dev/sr0 -check_md5 FAILURE --
Verification of each single data file that is still valid in the
most recent session, regardless in what session its data are located:
  xorriso -for_backup -indev /dev/sr0 -check_md5_r FAILURE / --
Verification of all sessions
  xorriso -for_backup -indev /dev/sr0 -check_media --
Listing files and their checksums (in md5sum format)
  xorriso -for_backup -indev /dev/sr0 -find / -type f -exec get_md5 --

Advantage of xorriso doing the reading: less drive rattling
because file access is sorted by the files' block addresses.
So the read lense will monotonously move outwards.

Further advantage: no mounting needed, no block device driver involved,
no eject-load cycle between writing and verifying.


Have a nice day :)

Thomas