I am not sure what you will see with an IDE device. Most likely this is all the information you need to have, as cdrecord polls the device and seems to default well. If this is not the case, grab the manual for your CD writer, type man cdrecord and start reading.
Optionally, the -v option gives you a little more information when the program is running. On my system, for example, I enter the following to write the SuSE 9. For comparison's sake, this is what the command's output looks like:. There is some useful information in there, as well as one very important piece of information. In the last line, cdrecord tells you if the FIFO ever was empty and how low it ever got. This is the buffer to the device.
You are transferring the data to the CD in real time. The minimum fill percentage is a good way to check how close you are to not keeping up. If this number gets fairly low, you should stop all unnecessary processes when you are writing a CD. Copyright c , LG Staff.
Originally published in Linux Gazette issue Copyright c , Specialized Systems Consultants, Inc. Since we're burning an ISO image here, I don't want to add any more data later in a future 'session', so I can just instruct cdrecord to put it in one session and finalise the disc. You can experiment with higher speeds if you want, but don't go higher than either your media or burner state they can do and do. After some interesting messages, the burn process should start and you should get a progress message showing you the amount of data that has been copied and some other diagnostic information.
Writing time: Fixating time: At this point, you can eject your disc and put it to use - however that may be!
0コメント