linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sunil Mushran <sunil.mushran@oracle.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Lukas Czerner <lczerner@redhat.com>,
	Andreas Dilger <adilger@dilger.ca>,
	linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH] e2fsprogs: Fix how we treat user-spcified filesystem size
Date: Wed, 02 Feb 2011 10:05:15 -0800	[thread overview]
Message-ID: <4D499CDB.80107@oracle.com> (raw)
In-Reply-To: <AANLkTi=5QWtEc+mRnveErm1AE4oLZAZwGOmLP69cx2dx@mail.gmail.com>

On 02/02/2011 09:56 AM, Greg Freemyer wrote:
>> Right, that's why there is the "rant" about it being called kilobytes,
>> but still treated as binary, not decimal unit. But Andreas is right
>> that it is not necessary to have one paragraph grumbling about the
>> stupid-sounding kibibytes and so on.
>>
>> So, what I am going to do is to cope with the standard and use those
>> stupid-sounding binary prefixes (kibi- etc.), remove the "rant" and add
>> one line note for people to be really sure that it is meant to be a
>> binary unit.
>>
>> Thanks!
>> -Lukas
> Lukas,
>
> I'm glad you did that.  I see too often:
>
> Fdisk is broken, I can only put a 150 gigabyte partition on my 160
> gigabyte drive.
>
> Hopefully people will realize the difference when they see its a 150
> Gibibyte partition on a 160 Gigabyte drive.

That's wishful thinking.

      reply	other threads:[~2011-02-02 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 19:18 [PATCH] e2fsprogs: Fix how we treat user-spcified filesystem size Lukas Czerner
2011-02-01 20:37 ` Andreas Dilger
2011-02-01 21:08   ` Lukas Czerner
2011-02-01 21:57   ` Greg Freemyer
2011-02-02 10:12     ` Lukas Czerner
2011-02-02 17:56       ` Greg Freemyer
2011-02-02 18:05         ` Sunil Mushran [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=4D499CDB.80107@oracle.com \
    --to=sunil.mushran@oracle.com \
    --cc=adilger@dilger.ca \
    --cc=greg.freemyer@gmail.com \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).