http://www.google.com/search?hl=en&d...ition&ct=title
i think you understand, but it's just hard to believe. with k3b, k3b is the frontend, and mkisofs, cdrecord, and cdrdao are the backends.
I don't use a frontend anymore. I just have a couple of scripts that i use to create an iso and burn it for dvd's, but i do use a frontend, simplecdrx for making audio cdroms.
I put the files i want to burn to a dvd in a directory.
I have a script on my machine called mkisofs.sh.sh that makes an iso image.
/usr/local/bin/mkisofs -r -joliet-long -l -o $1 .
which takes one variable. The name and path where the iso image will be written. The $1 holds that variable. I put it in the same place usually /2/dvd.iso.
I have a burning script that calls cdrecord that burns the iso image to disks in 2 different drives called cdrecord.both. This is it.
exec nice -n -2 cdrecord dev=ATA:1001,0,0 fs=96m gracetime=5 -v -dao -force -speed=16 -data -driveropts=burnfree "$@" &
exec nice -n -2 cdrecord dev=ATA:1002,0,0 fs=64m gracetime=4 -v -dao -force -speed=16 -data -driveropts=burnfree "$@"
So, I put 4.5 gigs of data in a directory, cd into that directory, and run mkisofs.sh.sh /2/dvd.iso && cdrecord.both /2/dvd.iso
The mkisofs.sh.sh script makes the iso, the && continues if there is no error, and the cdrecord.both makes the 2 copies.
I just wanted you to know what is possible.