[ANNOUNCE] ddpt, yet another dd variant

[Douglas Gilbert]

ddpt is yet another variant of the venerable Unix
dd command line utility. Some features found in
ddpt which are not found in the current (GNU) dd
implementation:

  - sparse writing (i.e. don't write buffer if all zeros)
  - write sparing (i.e. don't write buffer if already same
    as destination)
  - resume (after the copy has been interrupted)
  - trim on output of copy, self trim (pt interface only)
  - send output to a second file (see 'of2=' option)
  - access devices directly via pass-through interface,
    bypassing file system
  - accept numeric command line arguments in hexadecimal
  - explicit controls over how much data is read into the
    copy buffer and then written to output (separate from
    the logical block sizes of any device involved)

For those familiar with the sg3_utils package, ddpt is
a rewrite of the sg_dd utility. ddpt removes the special
support for the SCSI generic (sg) driver features found in
sg_dd. This allows ddpt to use other SCSI pass-throughs
such as bsg in Linux plus the SCSI pass-throughs found in
FreeBSD, Solaris and Windows.

ddpt has been almost 2 years in the making. Every time I
prepared to release it, the most frequent contributor to
this project, Mark Knibbs, would have another feature
request or correction in my Inbox. Time to get it out the
door.

Note that ddpt is not meant to be an exact replacement for
dd. ddpt changes some dd defaults. For example, if the output
file (i.e "of=") is not given, ddpt does not output anything;
dd will send the output to stdout which is not much fun if
the input is a terabyte of binary data.


The initial release version number is 0.91 . For more
information and downloads see:
    http://sg.danny.cz/sg/ddpt.html

A release announcement has been sent to freshmeat.net .

Doug Gilbert
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/