linux-kernel - RE: PROBLEM: KB->KiB, MB -> MiB, ... (IEC 60027-2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 20 Jan 2007 14:54:10 -0800
From:	"David Schwartz" <davids@...master.com>
To:	<linux-kernel@...r.kernel.org>
Subject: RE: PROBLEM: KB->KiB, MB -> MiB, ... (IEC 60027-2)


> Nice observation, however, it still leaves quite an amount of internal
> inconsistencies in the kernel output.

	I agree with the majority view that using the term 'MB' or 'GB' to mean a
million or a billion bytes is inaccurate. The way RAM and flash are measured
is correct. The way disk manufacturers advertise disk capacity is simply
*wrong*. There is no word for a million bytes. There is no word for a
billion bytes.

> One way of getting rid of those inconsistencies would be to follow IEC
> 60027-2 for those cases where SI is inappropriate.

	Talk about a cure worse than the disease! So you're saying that 256MB flash
cards could be advertised as having 268.4MB? A 512MB RAM stick is
mislabelled and could correctly say 536.8MB? That's just plain craziness.

	Adopting IEC 60027-2 just replaces a set of well-understood problems with
all new problems.

	DS


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