I've seen that bug, but I think our bug was more that dd would exit if it got
back a short read from input. So if you did something like this (maybe not
exactly, but close):
dd bs=1m | dd bs=10m > f.out
You might get only 1mb in f.out. This had to do with skipping disklabels and
other such
On 8 Mar, Devin Teske wrote:
> Problem we had found was:
>
> Executing dd with a closed stdout and stderr would cause the summary
> messages printed at the end to go into the destination output file.
>
> For example,
>
> dd if=/dev/zero of=/tmp/foo bs=1m count=1
>
> Works fine, but the
Problem we had found was:
Executing dd with a closed stdout and stderr would cause the summary messages
printed at the end to go into the destination output file.
For example,
dd if=/dev/zero of=/tmp/foo bs=1m count=1
Works fine, but the following:
dd if=/dev/zero of=/tmp/foo bs=1m count=1
Devin and I found this when we worked together. I think it was due to
some situation in dd(1) where short reads would exit pre-maturely,
however I may be mis-remembering. Devin, do you recall the specifics?
On 3/4/17 7:44 PM, Julian Elischer wrote:
an interesting point to discuss? is our
an interesting point to discuss? is our behaviour in this test right?
from: "austin-group mailng list (posix standard discussion)"
-- rest of email is quoted ---
On 5/3/17 5:48 am, Stephane Chazelas wrote:
2017-03-04 13:14:08 +, Danny Niu:
Hi all.
I couldn't remember where I
