Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S286274AbRL0Nry>; Thu, 27 Dec 2001 08:47:54 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S285134AbRL0Nrf>; Thu, 27 Dec 2001 08:47:35 -0500
Received: from mailout05.sul.t-online.com ([194.25.134.82]:33937 "EHLO
	mailout05.sul.t-online.com") by vger.kernel.org with ESMTP
	id <S286272AbRL0Nra>; Thu, 27 Dec 2001 08:47:30 -0500
Date: 27 Dec 2001 13:41:00 +0200
From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Message-ID: <8FeKiRymw-B@khms.westfalen.de>
In-Reply-To: <Pine.LNX.4.33L.0112211913360.28489-100000@duckman.distro.conectiva>
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: <20011221134034.B11147@thyrsus.com> <Pine.LNX.4.33L.0112211913360.28489-100000@duckman.distro.conectiva>
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

riel@conectiva.com.br (Rik van Riel)  wrote on 21.12.01 in <Pine.LNX.4.33L.0112211913360.28489-100000@duckman.distro.conectiva>:

> On Fri, 21 Dec 2001, Eric S. Raymond wrote:
>
> > What, and *encourage* non-uniform terminology?  No, I won't do that.
> > Better to have a single standard set of abbreviations, no matter how
> > ugly, than this.
>
> Last I checked the purpose of language was _communication_.
>
> Better use words people understand.

People in general *don't* understand the current so-called "established  
practice", because not only is it inconsistent with all of the rest of the  
world, it's also inconsistent with itself.

A few specialists such as you or me understand those terms in those few  
areas we are familiar with.

> Also, the kB vs KiB mess is so ambiguous and complex that

What is ambiguous or complex about it?

> As a last point, we shouldn't forget about the inconsistent
> way in which the marketing departments of hardware vendors
> apply these units to their products.

Do you know of *any* case where KiB and friends have been applied  
inconsistently? You may not be arguing the side you seem to want to be  
arguing here ...

> In many cases binary
> and decimal units are mixed, leading to something which is
> impossible to "get right".  Disk space would be one example
> of this, but I'm sure there are more.

I have no idea why you think it is impossible to get right. It is fairly  
easy to get right. Of course, that means using different numbers, but then  
I've been saying for more than a decade that those numbers are a lie.


MfG Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/