From: Pádraig Brady <P@draigBrady.com>
Date: Tue, 8 May 2012 12:18:45 +0000 (+0100)
Subject: doc: clarify dd conv=sparse usage with devices
X-Git-Tag: v8.17~8
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=be2dabef95d5638e40c7c74b2bc1a3a4dd64bae3;p=platform%2Fupstream%2Fcoreutils.git

doc: clarify dd conv=sparse usage with devices

* doc/coreutils.texi (dd invocation): Clarify that NUL blocks
are not copied for devices either, and give examples of where
it might be useful.
---

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 61b3c89..767267b 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -8167,9 +8167,12 @@ On a file system that supports sparse files, this will create
 sparse output when extending the output file.
 Be careful when using this option in conjunction with
 @samp{conv=notrunc} or @samp{oflag=append}.
-With @samp{conv=notrunc}, existing data in the output
+With @samp{conv=notrunc}, existing data in the output file
 corresponding to @sc{nul} blocks from the input, will be untouched.
 With @samp{oflag=append} the seeks performed will be ineffective.
+Similarly, when the output is a device rather than a file,
+@sc{nul} input blocks are not copied, and therefore this option
+is most useful with virtual or pre zeroed devices.
 
 @item swab
 @opindex swab @r{(byte-swapping)}