GNU bug report logs - #12794
Bug in dd: it sends wrong messages to stderr

Previous Next

Full log

Message #21 received at 12794 <at> debbugs.gnu.org (full text, mbox):

From: Eric Blake <eblake <at> redhat.com>
To: Ganton <kubry <at> terra.com>
Cc: Paul Eggert <eggert <at> cs.ucla.edu>, 12794 <at> debbugs.gnu.org
Subject: Re: bug#12794: Bug in dd: it sends wrong messages to stderr
Date: Mon, 05 Nov 2012 14:48:44 -0700

[Message part 1 (text/plain, inline)]

On 11/05/2012 02:43 PM, Ganton wrote:

> Many ones will doubt that the POSIX standard is so broken that forces people 
> to see messages in stderr that are not errors and not wanted. That even goes 
> against the Unix philosophy, for example, against the "Rule of Silence: When a 
> program has nothing surprising to say, it should say nothing" 

Sorry, but dd is older than POSIX, and POSIX standardized existing
practice rather than forcing dd to change.  You're 40 years too late on
this one.

> Thanks for the information. If the user utilizes "dd status=noxfer", he gets 
> rid of lines like
> 	512 bytes (512 B) copied, 0,000129625 s, 3,9 MB/s
> in stderr, although he keeps seeing lines like
>         1+0 records in
>         1+0 records out
> in stderr. Does anyone think a new report bug should be filled so that an 
> optional dd parameter could eliminate that last kind of messages from stderr?

No need to report a new bug - we already told you that coreutils 8.20
added 'dd status=none' to silence even that information.

-- 
Eric Blake   eblake <at> redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

[signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.