Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Mar 2021 17:07:01 -0500
From:      grarpamp <grarpamp@gmail.com>
To:        freebsd-standards@freebsd.org
Cc:        freebsd-questions@freebsd.org
Subject:   Standards: IEC Giga [re: FreeBSD image size confusion]
Message-ID:  <CAD2Ti29KTgFTEnJFNa_X61Tv+HWx4KSB30vmDdERmYCjx9USEg@mail.gmail.com>

Next in thread | Raw E-Mail | Index | Archive | Help
> is in true GBs

"true" is not a modifier of any prefix or unit in any standard,
though false GB are what's reported by USB firmware in
cheapo USB drives from some sketchy vendors ;)

> 4.5 GigaBytes means 4.5 GiB.

4500000000 does not equal or "mean" 4831838208.

International Standards IEC (re ISO/SI/Metric)...
"giga" = "G" = decimal prefix, powers of ten, 10^, base 10 underlying
"gibi" = "Gi" = binary prefix, powers of two, 2^, base 2 underlying
There is no such prefix as "K", it's "kilo k" or "kibi Ki".
"B"yte is 8 "b"its.
RAM is in binary 2^.
Physical storage DVD/BR/USB/disk/tape/etc (quotable in decimal 10^
on the box [1]), filesystem and files UI presentation displayable in
binary prefix, use correct underlying math.
Rest in decimal 10^, including...
Network bandwidth rates... routers switches OS interfaces hardware interfacing
upstream, constant bandwidth rate managed network centric app software
[filesharing,
overlays, even packet filters]... in [kMGT...]bps ("b"its/sec) ie:
100Mbps, not the "bi"
prefixes, nor even "B"ytes... with counters in bytes not bits.
Contexts pair their associated "prefix, to base unit, to underlying math",
ie: kilometers distance (km) not kibimeters (Kim), mebibytes RAM (MiB)
not megabytes (MB), gigabps network rates (Gbps) with tier level ISPs
not gibibps (Gibps). Silly bytes per period referenced transfer notation
(B/sec, B/day, B/mon) of legacy small webhosters, and phone extortion
billing models, that all calculate and use average bitrate with upstream
already anyway... orthagonal and falling off.

Many areas in FreeBSD could be checked for representation...
prefixes for disk space using decimal G instead of binary Gi,
places under a given context (netrates or diskspace) but displaying
mixed representations across their respective utilities in base, etc.

Rockets crash due to perpetuating use of nonstandard / mix legacy.
Representations could look towards some newer formal standardization
than pre-2000's adhoc.

Linux seems to making some RAM/disk/netrates updates there with
"bi" prefixes now appearing in various places, do not know if they have
a standards conformance / base policy doc on that.

https://www.iso.org/standard/31898.html  IEC 80000-13:2008
https://www.electropedia.org/iev/iev.nsf/display?openform&ievref=112-01-27
https://en.wikipedia.org/wiki/Binary_prefix
https://en.wikipedia.org/wiki/Unit_prefix

[1] Pre :2008, WDC and STX lawsuits forced more disclosure and market
consistency,
still annoying to convert box/nameplate/sector decimal <--> logical binary.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CAD2Ti29KTgFTEnJFNa_X61Tv+HWx4KSB30vmDdERmYCjx9USEg>