Status: closed
Thank you Pádraig,
for the info about the new upstream dd status=none closing the bug!
http://pubs.opengroup.org/onlinepubs/007904875/utilities/dd.html does for
stderr indeed command the block counts and allow extra diagnostic messages
like transfer rate.
http://www.gnu.org/software/coreutils/manual/coreutils.html#dd-invocation
assures me the new status=none means "Do not print any informational or
warning messages to stderr. Error messages are output as normal."
I would linguistically guess for status=none to basically mean 2>/dev/null
status=noinfo,nowarn,noerror,noxfer instead of status=noinfo,nowarn,noxfer
and would still be thinking I might want a less dangerous
status=noposixcounts (status=noinfo+noxfer) or even require an explicit
status=gnu/xfer (status=errors+warnings+posixcounts+transferbitrate).
But that can wait until I learned the best syntax to fork out from
reportbug and temporarily replace coreutils:stable with coreutils:testing
or coreutils:unstable or fire up a functional gdb /bin/dd to patch around.
Cheers: Rome
2014-06-16[Mon]12:53 Roman Czyborra read:
2014-06-15[Sun]20:42 Pádraig Brady wrote:
On 06/15/2014 06:10 PM, Roman Czyborra wrote:
Package: coreutils
Version: 8.13-3.5
Severity: normal
I would expect "suppress transfer statistics" to do away with the
"records in" at successful operation:
The records count is a POSIX specified output that _shall_ be output.
One can only control the non POSIX transfer statistics with status=noxfer.
Since coreutils 8.20 there is the new status=none option to suppress all
info and warning messages.
