Re: possible bug - output stream handling inconsistency in dd

2005-11-07 Thread Paul Eggert
"Theodoros V. Kalamatianos" <[EMAIL PROTECTED]> writes: > Did anyone review the patch, or did it slip through the cracks ? I'd > really like to know if I need to imrove on this... I haven't had the time to look at it yet. coreutils is still in a feature freeze so it's not pressing. ___

Re: possible bug - output stream handling inconsistency in dd

2005-11-04 Thread Theodoros V. Kalamatianos
On Wed, 2 Nov 2005, Theodoros V. Kalamatianos wrote: Anyway, I _think_ that following patch implements the desired behaviour: Did anyone review the patch, or did it slip through the cracks ? I'd really like to know if I need to imrove on this... Regards, Theodoros Kalamatianos _

Re: possible bug - output stream handling inconsistency in dd

2005-11-01 Thread Theodoros V. Kalamatianos
On Tue, 1 Nov 2005, Paul Eggert wrote: "Theodoros V. Kalamatianos" <[EMAIL PROTECTED]> writes: lseek is valid on e.g. /dev/hda and people would not expect dd to null their data till it reached the desired offset. True. I guess the algorithm should be to use lseek if possible, and to write n

Re: possible bug - output stream handling inconsistency in dd

2005-11-01 Thread Paul Eggert
"Theodoros V. Kalamatianos" <[EMAIL PROTECTED]> writes: > lseek is valid on e.g. /dev/hda and people > would not expect dd to null their data till it reached the desired > offset. True. I guess the algorithm should be to use lseek if possible, and to write nulls otherwise. Then ftruncate if pos

Re: possible bug - output stream handling inconsistency in dd

2005-11-01 Thread Theodoros V. Kalamatianos
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 t

Re: possible bug - output stream handling inconsistency in dd

2005-10-31 Thread Paul Eggert
"Theodoros V. Kalamatianos" <[EMAIL PROTECTED]> writes: > So I guess we have to fix dd to output null bytes to stdout, correct? 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. _

Re: possible bug - output stream handling inconsistency in dd

2005-10-31 Thread Theodoros V. Kalamatianos
On Mon, 31 Oct 2005, Paul Eggert wrote: Before proceeding too far in this matter can you please check the compatibility of your solution with the proposed action in XCU ERN 64? Please see and look for 'Enhancement Request Number 64'.

Re: possible bug - output stream handling inconsistency in dd

2005-10-31 Thread Paul Eggert
Before proceeding too far in this matter can you please check the compatibility of your solution with the proposed action in XCU ERN 64? Please see and look for 'Enhancement Request Number 64'. Thanks.

Re: possible bug - output stream handling inconsistency in dd

2005-10-31 Thread Theodoros V. Kalamatianos
On Mon, 31 Oct 2005, Theodoros V. Kalamatianos wrote: I think that the proper behaviour would be to ftruncate() the output file only when it is larger than the requested seek size. Hmm, I seem to have forgotten that what _I_ think doesn't really matter that much :-). So I just checked the IEE