From: Josh Boyer <jdub@us.ibm.com>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
tglx@linutronix.de, "Robert P. J. Day" <rpjday@mindspring.com>,
MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: running out of space dd'ing JFFS2 image to /dev/mtdblock/0
Date: Mon, 31 Jan 2005 11:29:11 -0600 [thread overview]
Message-ID: <1107192551.7567.31.camel@windu.rchland.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0501311722120.17207@phoenix.infradead.org>
On Mon, 2005-01-31 at 17:25 +0000, Artem B. Bityuckiy wrote:
> On Mon, 31 Jan 2005, [iso-8859-1] Jörn Engel wrote:
>
> > On Mon, 31 January 2005 17:11:38 +0000, Artem B. Bityuckiy wrote:
> > > On Mon, 31 Jan 2005, Robert P. J. Day wrote:
> > >
> > > > i agree completely, but i thought some of the recognized suffixes were
> > > > "KiB", "MiB" and so on. anyway, i was pretty sure that even a
> > > > suggestion this innocuous was going to generate some discussion.
> > > Nobody told about not to use KiB/MiB. It wos told about not to us K and M,
> > > like 10K, 100M. Use 10KiB, 100MiB instead.
> >
> > What information does the "B" in "10KiB" contain? And why is it "Ki"
> > instead of the correct "ki"?
> Hehe.
>
> This is just widely used unit. And it is usually written like that. And
> now most utilities work with such. But if one wants and thinks it is
> reasonable, why not to use kib :-)
Because they aren't just commonly used units. See:
http://physics.nist.gov/cuu/Units/binary.html
josh
next prev parent reply other threads:[~2005-01-31 17:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 15:14 running out of space dd'ing JFFS2 image to /dev/mtdblock/0 Robert P. J. Day
2005-01-31 15:21 ` Josh Boyer
2005-01-31 15:43 ` Robert P. J. Day
2005-01-31 15:54 ` Artem B. Bityuckiy
2005-01-31 16:14 ` Robert P. J. Day
2005-01-31 16:22 ` Artem B. Bityuckiy
2005-01-31 16:22 ` Thomas Gleixner
2005-01-31 16:26 ` David Woodhouse
2005-01-31 16:51 ` Robert P. J. Day
2005-01-31 17:11 ` Artem B. Bityuckiy
2005-01-31 17:21 ` Jörn Engel
2005-01-31 17:25 ` Artem B. Bityuckiy
2005-01-31 17:29 ` Josh Boyer [this message]
2005-01-31 17:38 ` Jörn Engel
2005-01-31 17:29 ` Jörn Engel
2005-01-31 17:43 ` Robert P. J. Day
2005-01-31 17:52 ` Jörn Engel
2005-01-31 18:22 ` Robert P. J. Day
2005-01-31 18:31 ` David Woodhouse
2005-01-31 19:02 ` Robert P. J. Day
2005-01-31 22:30 ` Robert P. J. Day
2005-01-31 16:39 ` Jörn Engel
2005-02-01 0:19 ` David Woodhouse
2005-02-01 0:43 ` Josh Boyer
2005-02-01 13:03 ` Jörn Engel
2005-01-31 16:01 ` Jörn Engel
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=1107192551.7567.31.camel@windu.rchland.ibm.com \
--to=jdub@us.ibm.com \
--cc=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rpjday@mindspring.com \
--cc=tglx@linutronix.de \
/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