>It took 14 years for GNU devs to ad progress in the command
dd status=progress
it works beautifully but... why are they so incompetent and lazy?
It took 14 years for GNU devs to ad progress in the command
Benjamin Bell
Other urls found in this thread:
freebsd.org
twitter.com
Kevin Richardson
yeah it's surprising that it took that long, but this really isn't GNU being particularly lazy, as *BSD dd still doesn't have it.
Grayson Butler
Imagine adding a single, small feature to something like cat and introducing a bug that you had absolutely no way to foresee because of how widespread it is. You just broke software that has had well defined behaviors and even "well defined bugs" and is universally adopted on basically every *nix based box on the planet. All to add a meaningless feature.
That's why it took them 14 years to do. And even then, they probably shouldn't have.
Levi Green
That's because C is a dying language, it's rather hard to find a useful Ctard these days.
Gabriel Ramirez
Imagine thinking you know anything about writing software. Have you even heard of regression tests?
Wyatt Bell
You're retarded.
Connor Morris
>adding a simple command output generate bugs
incompetent devs
Adam Cruz
looks nice though
dbz [ ~ ]$ dd status=progress if=/dev/zero of=test.file
137200640 bytes (137 MB, 131 MiB) copied, 10 s, 13.7 MB/s
Bentley Jackson
It's a bit more unwieldy, but you still had this option prior to that, in the man pages:
Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying.
Ian Lewis
dd status=progress if=/dev/zero of=/dev/sda
Wow, it works. Nice improvement, you should test it.
Angel James
No it isn't, it prints the progress on stderr instead of stdout. I do not agree with this decision.
Jack Allen
This. OTOH it is very weird that they stuck with just that for so long, and arguably stderr seems wrong.
Maybe just continue with ddrescue.
Wyatt Sullivan
Did you have a regression test for holding the space bar making the CPU overheat?
James Hill
This has worked for ages.
dd if=input | pv | dd of=output
Nicholas White
Imagine thinking you know about maintaining software but not understanding basic SOLID shit like open/closed principle.
Brayden James
>pv
it didn't work 3 years ago
Elijah Morris
what does
dd if=/dev/input of=/dev/output && sync do? why two &?
Nolan Miller
>why two &
man bash
AND and OR lists are sequences of one or more pipelines separated by
the && and || control operators, respectively. AND and OR lists are
executed with left associativity. An AND list has the form
command1 && command2
command2 is executed if, and only if, command1 returns an exit status
of zero.
Jeesus fuck you can't be that lazy
Zachary Gonzalez
dd should be considered harmful
Robert Kelly
>it prints the progress on stderr instead of stdout
Are you retarded? Where else would it output except stderr? If it outputted to stdout, you couldn't pipe DD output.
Jackson Russell
Yeah, well GNU is still ahead of the game. E.g. GNU coreutils du has -b for bytes, while BSD doesn't.
Justin Rivera
>GNU coreutils du has -b for bytes, while BSD doesn't.
freebsd.org