[prev in list] [next in list] [prev in thread] [next in thread] 

List:       coreutils-bug
Subject:    Fwd: dd (coreutils) 5.97 used power of 10 not 2 for calculating MB
From:       "Dat Head" <dathead2 () gmail ! com>
Date:       2007-01-23 21:15:54
Message-ID: 5c01594c0701231315y208c1944j7addbeca67e9b5b2 () mail ! gmail ! com
[Download RAW message or body]

i'm not saying any of this needs to happen, just something that i noticed.

instead of another flag it might be easiest to just make the stderr message
match whatever was specified in the bs= option (e.g. if you use M then
use ^2 in stderr, if you use MB then use ^10)  of course what to do
when ibs= specifies one way and obs= specifies another is a whole
'nother story!

earlier somebody mentioned MiB usually stands for ^2  is that right!?,
i always thought that the "i" between the MB was from million (as
opposed to mega)

On 1/23/07, Paul Eggert <eggert@cs.ucla.edu> wrote:
> Pádraig Brady <P@draigBrady.com> writes:
>
> > There is support for binary multiples in dd,
>
> Yes, but that's for the operands of dd, e.g., "dd bs=512M" talks about
> a block size 512 * 1024 * 1024 bytes, as opposed to "dd bs=512MB"
> which uses 512 * 1000 * 1000.  But Dat Head is asking for binary
> multiples in the stderr messages, e.g.,
>
>    $ dd bs=512M count=1024 if=/dev/zero of=/dev/null
>    1024+0 records in
>    1024+0 records out
>    549755813888 bytes (550 GB) copied, 13.7008 s, 40.1 GB/s
>
> Currently these messages always use powers of 10, not 2, even if the
> block size and counts are powers of 2.  Dat Head wants that last line
> to say "(512 GiB)" and "37.4 GiB/s".  That will require a new option,
> I think.



[prev in list] [next in list] [prev in thread] [next in thread]