From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S286309AbRL0OVP>; Thu, 27 Dec 2001 09:21:15 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S281895AbRL0OVH>; Thu, 27 Dec 2001 09:21:07 -0500
Received: from mailout06.sul.t-online.com ([194.25.134.19]:13520 "EHLO
	mailout06.sul.t-online.com") by vger.kernel.org with ESMTP
	id <S286300AbRL0OUy>; Thu, 27 Dec 2001 09:20:54 -0500
Date: 27 Dec 2001 14:10:00 +0200
From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Message-ID: <8FeKjMmXw-B@khms.westfalen.de>
In-Reply-To: <1008883684.4704.0.camel@localhost.localdomain>
Subject: Re: Configure.help editorial policy
X-Mailer: CrossPoint v3.12d.kh8 R/C435
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Organization: Organisation? Me?! Are you kidding?
In-Reply-To: <Pine.LNX.4.33.0112201605310.9934-100000@coffee.psychology.mcmaster.ca> <Pine.LNX.4.33.0112201605310.9934-100000@coffee.psychology.mcmaster.ca> <1008883684.4704.0.camel@localhost.localdomain>
X-No-Junk-Mail: I do not want to get *any* junk mail.
Comment: Unsolicited commercial mail will incur an US$100 handling fee per received mail.
X-Fix-Your-Modem: +++ATS2=255&WO1
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

reid.hekman@ndsu.nodak.edu (Reid Hekman)  wrote on 20.12.01 in <1008883684.4704.0.camel@localhost.localdomain>:

> On Thu, 2001-12-20 at 15:07, Mark Hahn wrote:

> > > 1024 decimal kilobyte disk
> > > 8.4 decimal gigabyte disks

> > though as your example showed, there's very little, if any,
> > ambiguity: disk is always decimal, memory is always binary, etc.

Ah, but the problem with this is that it's *wrong*.

Disk is not always decimal. Nor is it always binary. Most disk sizes are  
an unholy mixture of the two that deserves a stake through the heart,  
where 1 GB = 1,024,000,000 bytes.

If even people here do not understand how this works, then can it possibly  
be the right way of doing things?!

> More importantly, less educated users than yourself might not strike up
> the distinction between disk and memory units. The common example being,
> "why does my 9.1GB hard drive show up as 8.9GB?" Rather than explain

A current "9.1GB" hard disk would, if dc didn't lie to me, be either 9.3  
GB (decimal) or 8.7 GiB (binary).

> For me, my reasons for full names are consistency and aesthetics --
> allowing us to sidestep the abortion that the IEC has created of SI
> units.

So you'll be saying "9.3 milliards of bytes" - or is it "billions" where  
you live?

MfG Kai