Carl Lowenstein wrote:
On 6/9/05, Gus Wirth <[EMAIL PROTECTED]> wrote:
At 00:15 06/09/2005 -0700, Ralph Shumaker wrote:
I seem to recall something about "dd" to create a floppy from a
downloaded "*.img" file. "man dd" doesn't seem to give me the info I need.
Can anyone show me the recipe? Please?
$ dd if=your-disk-image.img of=/dev/fd0 bs=512
where
dd = command
if = input file
of = output file (remember, just about everything is treated like a file,
even if it's a device)
bs = block size
You probably don't really need the block size part, as all the bytes will
still make it onto the the disk. One thing you should do before putting the
image on the floppy is to format the floppy and check it for bad blocks.
That way you won't have any missing data when the image is transferred.
Note that the default block size of dd(1) is 512, so you don't have to
specify it. Some hardware/software combinations copy floppies faster
if you specify "bs=18k" which is the amount of data that can be read
from a floppy without moving the head. But nowadays Linux buffering
seems to just read/write everything all at once. Be sure to wait for
the light on the floppy drive to go out, indicating that it is
finished doing its thing, because the Linux command-line prompt will
return to you as soon as the data is in a buffer ready to go, but
before the actual output transfer is finished.
Understood, and will do. But as an aside, presume (for the moment) that
I don't want that behavior. Can the "buffer" be disabled or bypassed
such that the prompt doesn't return until all is done (in which case it
would be good to specify "bs=18k")?
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
