[prev in list] [next in list] [prev in thread] [next in thread] 

List:       coreutils
Subject:    [PATCH] doc: clarify dd conv=sparse usage with devices
From:       Pádraig Brady <P () draigBrady ! com>
Date:       2012-05-08 12:47:15
Message-ID: 1336481235-3967-1-git-send-email-P () draigBrady ! com
[Download RAW message or body]

* doc/coreutils.texi (dd invocation): Clarify that NUL blocks
are not copied for devices either, and give examples of where
it might be useful.
---
 doc/coreutils.texi |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

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)}
-- 
1.7.6.4



[prev in list] [next in list] [prev in thread] [next in thread]