Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
On 02/27/2012 05:09 PM, PƔdraig Brady wrote:
> how
> to handle existing regular files with conv=trunc.
> I.E. seeking over existing possible non NUL data.
> It's too dangerous/inconsistent to do this for files I think.
Why? This is *dd* we're talking about here.
It's *supposed* to be used for tricky stuff like this.
If one interprets conv=sparse to mean "write sparsely",
rather than "create a sparse file that exactly mimics
the input's sparseness", then everything should be clear,
no?