From owner-freebsd-questions@freebsd.org Sat Mar 13 22:07:04 2021 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D3E675ACCE6; Sat, 13 Mar 2021 22:07:04 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DycGv6pShz3kjc; Sat, 13 Mar 2021 22:07:03 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by mail-ed1-x532.google.com with SMTP id u4so12925638edv.9; Sat, 13 Mar 2021 14:07:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=6LrvjSDlNJhm8/Uxn8sNXkchbjOSouXZGvIJHo5hQOs=; b=mjf8xnUIkY7AqwYnPJ9mHxLx2t1nsvFCQcGHaNIvpd8OQJJnhXfO1tQ8WxEclti8S2 8/5VHUx8NPMlzkK7MPFd1BMaf/PL4vpNcqG+OaT3iqVzlPEzWJ2LrvnkAvsEQRGQkoo3 4358dzidod5M8YnOTD2PIYGUcRa/19F79WccBvay3CeDlGHTVYJuEL4XLlf2Ug0Upm/E sQ9T1Psk9CbIDdt35DRjHIzkic/gyu4MpxvzK3FAvxfJbBT2pIy+mbQyVOf0gihyXT15 jb9xY2zWlJ+5CESQqmUa56mhgrtgAaKnJuv2qRD/uvxUveZww/689z0oMPV87ARSDQ5p Q99A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=6LrvjSDlNJhm8/Uxn8sNXkchbjOSouXZGvIJHo5hQOs=; b=d4FvQvQOGtT8//8u6ixG390wLyOaul6SUoUFBsST7iXOTB/oJipemjOViLvh/rrrzS 26KZGElIf3x5KmYbfakkul9jZHQD1nZErQAeICPIXjd/ywxrkF+MgltYdBKYbW604cPC ArgWLw4/TWfOEVGj0lfaGvwW2YGzKbckBUL5d0RFh3fdOIoL2pDl56saDOSB8L4jXn1s Trvo/c/GoHPFsxFMgC7m9ZlsEZZLupVH1NQynL7ICqO0jxJir6LZQXtK8bAFHAPyRegx B7Sova3QwqjLpO3dQ5InCC9AjvAdpZZQOVJ42JQIhJDYCHldXXpkfl3P2lW6W7miqxnm 5EZg== X-Gm-Message-State: AOAM530/NFHhwbp1AuM9/OunC6dBlPG884wH0MNwHk+/wz3UdLOgzWPm RhpEg3uCRtwytCCiQyqyZpCU5dto3eq1OOGKne+hCexzhxQCjA== X-Google-Smtp-Source: ABdhPJxh7vfWKWqAZsp5I700XA5jwG5Budjpgd79dNF9Wk5AENC7TYkIRaPxcaF5jV8yECuLMZ2SuLdgrCkQ6E9CTWE= X-Received: by 2002:aa7:dbd3:: with SMTP id v19mr21713397edt.314.1615673221676; Sat, 13 Mar 2021 14:07:01 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a50:34c2:0:0:0:0:0 with HTTP; Sat, 13 Mar 2021 14:07:01 -0800 (PST) From: grarpamp Date: Sat, 13 Mar 2021 17:07:01 -0500 Message-ID: Subject: Standards: IEC Giga [re: FreeBSD image size confusion] To: freebsd-standards@freebsd.org Cc: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4DycGv6pShz3kjc X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=mjf8xnUI; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of grarpamp@gmail.com designates 2a00:1450:4864:20::532 as permitted sender) smtp.mailfrom=grarpamp@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::532:from]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_ALL(0.00)[]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::532:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::532:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-standards,freebsd-questions]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Mar 2021 22:07:04 -0000 > 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.