linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org, adilger@dilger.ca
Subject: Re: [PATCH 2/2] mke2fs: use binary units in the man page
Date: Sun, 6 Feb 2011 20:01:36 -0500	[thread overview]
Message-ID: <20110207010136.GD10402@thunk.org> (raw)
In-Reply-To: <1296643439-13908-2-git-send-email-lczerner@redhat.com>

On Wed, Feb 02, 2011 at 11:43:59AM +0100, Lukas Czerner wrote:
> Decimal units (kilobyte 10^3, megabyte 10^6 etc...) were used in
> mke2fs manual page, however they was really meant to be binary units
> (kibibyte 2^10, mebibyte 2^20 etc...), so change the man pages to
> reflect that fact, even if it sounds weird.

Ugh.  Even Don Knuth agrees that the names sound stupid.  (Of course,
his proposal of MMB and GGB haven't really gained much traction,
either.)

I guess I'm willing to tolerate MiB and GiB, but since most people
will ignore the 'i' and pronounce them as "Megabyte" in everyday
speech.  I really don't want to see "mebibyte or tibibytes" spelled
out explicitly anywhere, though.  :-(

And I think KiB is just wierd; I'm much rather see "1024 byte blocks"
than see "1 KiB blocks".

Personally I think the names are doomed.  Even the editors for IEEE
and ANSI journals aren't enforcing this in style guidelines; memory
manufacturers are ignoring the IEC names entirely, and certain most
humans never use those names in every day speech.

       	     	       	     	      	  - Ted

  reply	other threads:[~2011-02-07  1:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 10:43 [PATCH 1/2] e2fsprogs: Fix how we treat user-spcified filesystem size Lukas Czerner
2011-02-02 10:43 ` [PATCH 2/2] mke2fs: use binary units in the man page Lukas Czerner
2011-02-07  1:01   ` Ted Ts'o [this message]
2011-02-07 11:10     ` Lukas Czerner
2011-02-02 11:17 ` [PATCH v3 1/2] e2fsprogs: Fix how we treat user-spcified filesystem size Lukas Czerner

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=20110207010136.GD10402@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).