You're absolutely right. Thanks for catching that.
Though I've done a fair amount of work in binary I never got so I think
in binary. I bought my first "Hexalator in the mid. '70s. I should have
made more use of my current hexalator while writing this.
Some how I just got thinking about how there are usually more bytes on a
disk than the advertised number of bytes. I was thinking of how hard
drive technical spec's usually say bytes per sector and then guaranteed
number of sectors and if you multiply you get more than the advertised
number. They do that because some sectors are mapped out as bad during
factory test and the left over good ones end up being more than the
However, given how different OSs like to show different numbers (GB vs
GiB) and that can vary depending on how many sectors have been mapped
out, I will just strip the those sort of things out of the article.
Yes, I'm aware of the situation with SSDs. They switch out blocks of
memory all the time and that can lead to security problems.
Have a Great Day!
On 10/30/19 12:53, Gregory Lee Bartholomew wrote:
> Hi Pat:
> I just took a peak at your article. It looks good. FYI, I think the following
> sentence may be inaccurate:
> "These actual capacities are usually slightly larger than the decimal based
> number on the box or advertisement."
> I always heard that the advertisers INTENTIONALLY use the decimal-based number
> because it comes out slightly larger (i.e. 1TB looks better than 931GiB). From
> Software reports hard disk drive or memory capacity in different forms using
> either decimal or binary prefixes. The Microsoft Windows family of operating
> systems uses the binary convention when reporting storage capacity, so an HDD
> offered by its manufacturer as a 1 TB drive is reported by these operating
> systems as a 931 GB HDD. Mac OS X 10.6 ("Snow Leopard") uses decimal
> when reporting HDD capacity. The default behavior of the df command-line utility
> on Linux is to report the HDD capacity as a number of 1024-byte units.
> The difference between the decimal and binary prefix interpretation caused some
> consumer confusion and led to class action suits against HDD manufacturers. The
> plaintiffs argued that the use of decimal prefixes effectively misled consumers
> while the defendants denied any wrongdoing or liability, asserting that their
> marketing and advertising complied in all respects with the law and that no
> class member sustained any damages or injuries.
> There is a different issue where you might see that *SSDs* are, in actuality,
> "slightly larger", but the extra space in that case is not directly
> by the user. That extra space is really meant to compensate for manufacturing
> defects. Some of the data "cells" can fail prematurely and, rather than
> drive capacity gradually "shrink" as cells fail, the reserved/hidden cells
> substituted in when needed.
> There is also another hidden memory area in SSDs (
) that manufacturers and others
> use to hide software.
> Just FYI,
> On Wed, 2019-10-30 at 12:20 -0400, pmkellly(a)frontier.com wrote:
>> I received a review and made changes to: #27 Disk space maths, but I
>> can't move it back to Review. If I grab it and move it to review, it
>> just snaps back to In Progress. Is that how I should leave it at this stage?
>> Have a Great Day!
>> Pat (tablepc)
>> Fedora Magazine mailing list -- magazine(a)lists.fedoraproject.org
>> To unsubscribe send an email to magazine-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct:
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: