|
| From: | Theodoros V. Kalamatianos |
| Subject: | Re: possible bug - output stream handling inconsistency in dd |
| Date: | Tue, 1 Nov 2005 12:37:30 +0200 (EET) |
On Mon, 31 Oct 2005, Paul Eggert wrote:
It should still lseek and ftruncate, if stdout is a regular file, a directory (!), or a shared memory object. Otherwise I guess it has to write null bytes, yes.
What about special files ? lseek is valid on e.g. /dev/hda and people would not expect dd to null their data till it reached the desired offset.
Perhaps dd should output null bytes only on FIFOs ? On a relative matter, what should dd do in the following case: $ echo -n AB > f $ echo -n ab | dd bs=1 seek=1 >> f What should the contents of `f' be ?
| [Prev in Thread] | Current Thread | [Next in Thread] |