From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: linux-kernel@vger.kernel.org
Subject: Re: [OT] Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel p.
Date: Fri, 21 Dec 2001 00:12:40 +0100 [thread overview]
Message-ID: <3C227068.60803@gmx.at> (raw)
In-Reply-To: <B51F07F0080AD511AC4A0002A52CAB445B2A20@ottonexc1.ottawa.loran.com> <WHITEGtPrPrvCWO6hm8000002fb@white.pocketinet.com> <20011220204326.D5235@khan.acc.umu.se>
[snip]
David Weinehall wrote:
>>>(no, i'm not arguin, i don't particularly care. but i'm
>>>pointing out that some people have completely firmly set
>>>definitions and some other people also have firm definitions
>>>and neither will agree the other's right. MiB is the international
>>>standard for a 2^10 B(yte) specification. so if you mean
>>>2^10 bytes, you mean MiB, not MB, even if you don't like it :)
>>>
>>This "international" standard seems to have excluded a few countries.
>>It wasn't until it was SET that I even heard of its existance. (And
>>then only through SLASHDOT!)
>>
>>Everyone I know has been using KB/MB/GB for 1024 forever. The *only*
>>exception is networking, and the occasional FLASH/ROM size. The latter
>>isn't very common discussion, and among those that it is, they'd know
>>what the other was talking about. For the former, I can distinguish
>>easily depending on who it is.
>>
>>Someone without a lot of experience: I have a 1MB connection. (this
>>user has a 1 Megabit connection)
>>
>>Someone with experience: I have a 1mb/Mb connection. (This person has a
>>1 megabit connection has used a "standard" abbreviation.)
>>
>
> You have a 1 millibit per Megabit connection?!?!
Yeah, she/he uses compression! *ROFL* Sorry, couldn't resist! :)))
bye,
Wilfried
--
Terorists crashed an airplane into the server room, have to remove
/bin/laden. (rm -rf /bin/laden)
next prev parent reply other threads:[~2001-12-20 23:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 18:36 Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel p Dana Lacoste
2001-12-20 19:13 ` Nicholas Knight
2001-12-20 19:41 ` Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.help Mike Harrold
2001-12-21 16:59 ` Alan Cox
2001-12-21 17:50 ` Mike Harrold
2001-12-21 18:41 ` Kent Borg
2001-12-21 18:49 ` lk
2001-12-21 19:12 ` Kent Borg
2001-12-22 4:51 ` Albert D. Cahalan
2001-12-20 19:43 ` Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel p David Weinehall
2001-12-20 23:12 ` Wilfried Weissmann [this message]
2001-12-20 23:13 ` [OT] " Nicholas Knight
2001-12-20 23:03 ` ncw
2001-12-22 7:52 ` Mikael Abrahamsson
2001-12-22 12:53 ` Jeff Mcadams
2001-12-22 15:03 ` Dirk Moerenhout
2001-12-22 15:20 ` Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel Alan Cox
2001-12-22 16:10 ` Stephen Satchell
2001-12-22 17:43 ` Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel p mirabilos {Thorsten Glaser}
2001-12-22 22:21 ` Vojtech Pavlik
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=3C227068.60803@gmx.at \
--to=wilfried.weissmann@gmx.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.