[Cdrecord-support] Trying cdrecord to write data to DVD+R?

[Mark Knecht]

On Tue, Feb 16, 2010 at 5:52 AM, Michael Shell <list1 at michaelshell.org> wrote:
> On Mon, 15 Feb 2010 09:59:56 -0800
> Mark Knecht <markknecht at gmail.com> wrote:
>
>
>> cdrecord dev=1001,0,0 backup.tar.bz2
>
> To make an image, I use something like:
>
> mkisofs -V volume -R -J -v -o filename.img directories
>
> you can omit the -J if you aren't planning to use it under MS Windows.
> Note that directory *contents* are placed at root of image.
>
> Then burn via:
>
> cdrecord -v dev=1001,0,0 file.img
>
> You should then be able to mount it and see the file/files.

Thank you! This is making some sense, although see my response to
Joerg on why (to me) the use of cdrecord seems inconsistent to me.

None the less it doesn't matter. I need to learn how to use it and it
seems that mkisofs is the right wat to go.

>
>> I'm almost out of disk space on the system being backed up
>> and don't have another 5GB to create some big *.iso file.
>> Am I hosed?
>
> There is a wikihow article on on-the-fly burning with cdrecord,
> but I always build an image first so I don't have much experience
> here:
>
> http://www.wikihow.com/Use-CDR-Tools-On-the-Fly
>
> The growisofs burn utility operates by default in such an on-the-fly
> mode:
>
> growisofs -Z /dev/dvd -R -J /some/files
>
> Basically, in both cases mkisofs pipes its output to the burn utility.
> It's a good idea to have a machine that can keep up with the required
> data rate. Also, nothing better go wrong during mkisofs' work, or the
> burn will have to be aborted.
>

OK - makes sense. I don't know if that specific machine will keep up,
but I can drag the 4GB file across the network and do it on a machine
that certain will.

THANKS!

- Mark
>
>
>  Cheers,
>
>  Mike Shell
> _______________________________________________
> Cdrecord-support mailing list
> Cdrecord-support at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/cdrecord-support
>