News for hackers. Stuff that matters.
Re:Dd is not a disk writing tool (2015) by jff on Sunday January 08, 2017 @12:12PM (#13350709)
> Persistent progress indicators are known to cause performance degradation unless implemented carefully.

Are you referring to that npm progress bar thing a few months back? I'm pretty sure the reason for that can be summed up as "javascript, and web developers".

Anyway, he's not proposing progress bars by default, he's proposing a method by which you can query a process to see how far it's come. I think there's even a key combination to do this on FreeBSD.

Or, for example, you could write a small program that sends a USR1 signal every 5 seconds, splitting out the responsibility of managing a progress bar:

% progress cp bigfile /tmp/

And then the 'progress' program would draw you a text progress bar, or even pop up an X window with a progress bar.

Re:Dd is not a disk writing tool (2015) by hashhar on Monday January 09, 2017 @02:36AM (#13354679)
Re:Dd is not a disk writing tool (2015) by jff on Monday January 09, 2017 @11:15AM (#13357393)
That's great! I think due to the way it's implemented it wouldn't be able to do progress reporting for e.g. "dd if=/dev/zero of=bigfile bs=1M count=2048", but that's a less common case than just cp'ing a big "regular" file.
Re:Dd is not a disk writing tool (2015) by erikbye on Sunday January 08, 2017 @01:04PM (#13351000)
Yes, C-t for SIGINFO, works on all BSDs (including macOS).