From: Juergen Sawinski <juergen.sawinski@mpimf-heidelberg.mpg.de>
To: "linux-kernel@vger" <linux-kernel@vger.kernel.org>
Subject: B is Bel? b is Barn? [was RE: Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.help]
Date: 21 Dec 2001 13:41:03 +0100 [thread overview]
Message-ID: <1008938464.697.3.camel@nc1701d> (raw)
In-Reply-To: <B51F07F0080AD511AC4A0002A52CAB445B2A26@ottonexc1.ottawa.loran.com>
In-Reply-To: <B51F07F0080AD511AC4A0002A52CAB445B2A26@ottonexc1.ottawa.loran.com>
(Have a look at http://physics.nist.gov/cuu/Units/outside.html.)
Strictly speaking, "Byte" is actually a prefix, too. A prefix of the
number "1" - however, a prefix with a context. "bit", "rad" and others
are not real units, they are more like "context descriptions" off the
number "1".
I think, the prefixes "...T,G,M,k,m,µ..." should be taken, as they were
for a long time: context specific.
IMAO, if there is any sane way of defining this, it is by giving a base
as index (like the log function). In case of bit, Byte etc. -as they
already define a context- the base is always 2. In case of SI Base
Units, the base is 10.
But that's only my 0.5 Nibble cents/bit (oh, I mean Euro cents/bit).
George
P.S.: What's about using mole?
On Thu, 2001-12-20 at 20:27, Dana Lacoste wrote:
[...]
> there is _no_ standard for what 1MB means. There is a LOT of
> confusion, and most places will accept both
[...]
--
Juergen Sawinski
Max-Planck-Institute for Medical Research
Dept. of Biomedical Optics
Jahnstr. 29
D-69120 Heidelberg
Germany
Phone: +49-6221-486-309
Fax: +49-6221-486-325
priv.
Phone: +49-6221-418 848
Mobile: +49-171-532 5302
prev parent reply other threads:[~2001-12-21 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 19:27 Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel p Dana Lacoste
2001-12-21 12:41 ` Juergen Sawinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1008938464.697.3.camel@nc1701d \
--to=juergen.sawinski@mpimf-heidelberg.mpg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox