News for hackers. Stuff that matters.
Re:dd built-in progress introduced in coreutils 8.24 by mshook on Sunday January 10, 2016 @06:55PM (#10877859)
You could but letting dd take care of it instead of doing it yourself is much better IMHO.
Re:dd built-in progress introduced in coreutils 8.24 by zimbatm on Sunday January 10, 2016 @07:46PM (#10878069)
What if you started dd without status=progress ?
Re:dd built-in progress introduced in coreutils 8.24 by Gracana on Sunday January 10, 2016 @10:21PM (#10878586)
Updating dd to continuously dump text to the screen by default would probably break a lot of existing scripts.
Re:dd built-in progress introduced in coreutils 8.24 by zimbatm on Monday January 11, 2016 @04:53AM (#10879860)
Just on SIGUSR1 would be good enough to get an idea where dd is at. And it would be on stderr, not stdout.
Re:dd built-in progress introduced in coreutils 8.24 by Gracana on Monday January 11, 2016 @10:16AM (#10881181)
> it would be on stderr, not stdout

Oh, that's true.

Anyway, what behavior do you want to see exactly? You can still send the USR1 signal and get the update behavior just like before. Were you just pointing out that there are cases where you still need to use that feature, or something else?

Re:dd built-in progress introduced in coreutils 8.24 by neikos on Sunday January 10, 2016 @09:08PM (#10878353)
Then that's your own fault?
Re:dd built-in progress introduced in coreutils 8.24 by zimbatm on Monday January 11, 2016 @04:52AM (#10879858)
But surely if you could send a SIGUSR1 and get the progress it would be useful. I won't always have the foresight to put the progress argument. Maybe I expected the task to be quick but it's not.