Date: Mon, 26 Jan 2015 09:25:06 +0000 From: David Chisnall <theraven@FreeBSD.org> To: Vsevolod Stakhov <vsevolod@freebsd.org> Cc: svn-ports-head@freebsd.org, Alexey Dokuchaev <danfe@FreeBSD.org>, Baptiste Daroussin <bapt@FreeBSD.org>, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r377746 - head/ports-mgmt/pkg Message-ID: <AB13E957-D913-4BAD-B2AD-F3595BCBA989@FreeBSD.org> In-Reply-To: <54C277CA.8000609@FreeBSD.org> References: <201501231557.t0NFvKFE047114@svn.freebsd.org> <20150123160458.GA68670@FreeBSD.org> <54C277CA.8000609@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 Jan 2015, at 16:33, Vsevolod Stakhov <vsevolod@freebsd.org> wrote: >=20 > I'm personally happy to end the ambiguity between hard drive Terabytes > and network Tebibytes... A lot of HD manufacturers use one of the following two: 1KB =3D 1024 bytes 1MB =3D 1024 KB 1GB =3D 1000 MB 1TB =3D 1000 GB Or 1KB =3D 1024 bytes 1MB =3D 1000 KB 1GB =3D 1000 MB 1TB =3D 1000 GB Nothing that anyone sane does can make hard drive measurement units = comprehensible. Personally, one of the most confusing issues that I have with regard to = units is that FreeBSD and OS X have a number of command-line tools that = have a switch to toggle between binary and decimal prefixes, but the = switch has the opposite meaning on the two. We really need to have a = standard switch and/or environment variable for this that is consistent = across everything. I'd like to see that functionality be part of libxo, so that all = utilities can just produce unformatted numbers of bytes and have libxo = worry about the formatting when producing human-readable output and a = raw byte number when producing machine-readable formats. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AB13E957-D913-4BAD-B2AD-F3595BCBA989>