Xorriso CD/DVD burner software

Ttuuxxx provided a link to this in a recent blog comment. I have been in contact with the author, Thomas Schmitt, and he has been helpful regarding the bug I got with cdrkit and how Xorriso can replace 'mkisofs' and 'cdrecord'.

Here is the code that I recently posted, except replaced by Xorriso:

xorriso -as mkisofs \

-R -o cd-puppy.iso -b isolinux.bin -c boot.cat \
-no-emul-boot -boot-load-size 4 -boot-info-table ./build/

xorriso -as cdrecord \
-multi -tao -pad -data -eject -v speed=10 dev=/dev/sr0 \
cd-puppy.iso

SECT=`xorriso -as cdrecord -msinfo dev=/dev/sr0 | grep '^[0-9]*.[0-9]'`
export SECT
xorriso -as mkisofs \
-print-size -R -C $SECT -M /dev/sr0 -quiet \
-graft-points 2009-07-15=/root/nothing


I have created a xorriso PET package, with scripts named 'mkisofs' and 'cdrecord' that actually launch 'xorriso'. The variable MKISOFS is exported in /etc/profile.d/xorriso:

export MKISOFS="xorrisofs"

...as apparently the 'growisofs' utility in the 'dvd+rw-tools' package will read this variable and use 'xorrisofs' (a symlink to 'xorriso', behaves as 'mkisofs') instead of 'mkisofs'. But, as I have created a 'mkisofs' script anyway, the variable is not really needed.

I have also created 'cdrkit_cut' which has all the other utilities in cdrkit, except 'genisoimage' (mkisofs) and 'wodim' (cdrecord) removed.

The end result of all of the above is that everything should work as before, all cd/dvd burning scripts should work without any changes.

Testing
I have built a new pup with xorriso, cdrkit_cut and dvd+rw-tools packages. Xorriso is providing the 'mkisofs' and 'cdrecord' utilities that were previously in cdrkit.

I burnt an 4.21 Unleashed CD, 650MB, using 'burniso2cd', and all went well, and it verified correct.

But, I can't do much more testing. I'm away from home and my laptop does not support multisession burning. My relative has a PC with DVD-burner drive, but only 256MB of RAM -- which is a problem because I changed the init script so that more than 256MB of RAM is required before pup4-417.sfs is copied into RAM -- therefore the optical drive is mounted and a session can't be written to it.

Alright, I had better review that decision. I reckon that we do want multisession saving to work on PCs with 256MB RAM ...don't we? I'll look into that, do another build soon.


Posted on 17 Jul 2009, 21:22


Comments:

Posted on 18 Jul 2009, 6:36 by Leon
256 RAM limit
Yes, please!

Very appreciated goal of every new release!