begin: [EMAIL PROTECTED] <[EMAIL PROTECTED]> quote
>
> That would be nice, but it is in
>
> man dd
>
> if you interpolate:
>
> ---Quote---
> count=BLOCKS
> copy only BLOCKS input blocks
>
> ibs=BYTES
> read BYTES bytes at a time
> [...]
> obs=BYTES
> write BYTES bytes at a time
> [...]
> seek=BLOCKS
> skip BLOCKS obs-sized blocks at start of output
>
> skip=BLOCKS
> skip BLOCKS ibs-sized blocks at start of input
here's what i know:
cylinders are stacked circles.
heads are sides.
sectors are arcs.
tracks circles.
cluster are the smallest group of sectors a file can use.
maybe i'm not good at interpolating, but i'm still not understanding.
are you saying that a block is a cluster? is it a filesystem term or
a dd term?
pete
> <hypothesizing>There is something historical about dd that I never quite
> understood. It was described to me as a tool for converting data from
> storage on one type of device to storage on another, with 9-track tapes
> from various sources being common examples at the time it was described to
> me. Of course, I have only used a 9-track tape once, and that was on a
> VMS system, so I don't know much about them. I imagine that if a device
> driver could only support certain block sizes, a tool like dd would be
> useful for extracting data from tapes with an odd block size and putting
> it on tapes with a size more to your liking. I don't know if such
> restrictions remain in modern device drivers...</hypothesizing>
--
"The following addresses had permanent fatal errors..." [EMAIL PROTECTED]
-- Mailer Daemon www.dirac.org/p
