[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cdrecord image



Well, just issuing a command like:
cdrecord -dev=0,0,0 -v - cdimage.iso

starts the processes up and eventually gets to to:
Waiting for reader process to fill input buffer ...

And it just sits there like that forever.

Now, I'm assuming when you say to issue the command:
mkisofs -R -J -o cdimage.iso /directory

that /directory in this case is where the cdrom is mounted? or what?

Anyhow, I tried to do the following:
mkisofs -R -J -o cdimage.iso | cdrecord dev=0,0,0 -v -

But that didn't work. It immediately completed the job with:
Waiting for reader process to fill input buffer ... input buffer ready.
cdrecord: Premature EOF on stdin.
cdrecord: Input buffer error, aborting.
cdrecord: fifo had 1 puts and 0 gets.
cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%.

I've looked at the man pages, and I'm even more confused.

Curtis

On Wednesday, Feb 19, 2003, at 16:09 US/Pacific, Michael Wardle wrote:

On Thursday, February 20, 2003 10:07, Curtis Vaughan wrote:
In order to write files to a burner I issue the following command:
mkisofs -R -J /directory/with/files | cdrecord dev=0,0,0 -v -

However, I can't figure out how to issue the command to write an *iso
image to a writable CD. Can anyone help me?

You could always read the man pages for mkisofs and cdrecord. :-P

To create a CD image using mkisofs, add the -o option
(example: mkisofs -R -J -o cdimage.iso /directory)

To write a CD image using cdrecord, just specify the file name
(example: cdrecord -dev=0,0,0 -v- cdimage.iso)

I'm not too sure how reliable it is to use a pipe between the two; I
would be worried that using a pipe would make a buffer underrun more
likely.

--
Michael Wardle
Adacel Technologies



--



Reply to: