Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make consistent use of MiB (binary sizes) in GUI and tools and to avoid any misinterpretation #7889

Open
jamke opened this issue Nov 17, 2022 · 1 comment · May be fixed by QubesOS/qubes-manager#380
Assignees
Labels
C: other good first issue This is a recommended issue for first-time contributors. help wanted This issue will probably not get done in a timely fashion without help from community contributors. P: minor Priority: minor. The lowest priority, below "default." pr submitted A pull request has been submitted for this issue. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@jamke
Copy link

jamke commented Nov 17, 2022

How to file a helpful issue

The problem you're addressing (if any)

Currently Qubes OS uses "MB" to describe the size of 1024*1024 bytes. It has this disadvantages.

  1. You never know what MB is. It can be 2^20 bytes as in Windows, or 10^6 bytes as in memory and disk specifications.
  2. All other GNU+Linux-based OSes and almost all software for them uses "MiB", "KiB" and etc to avoid any misinterpretation. I think, Qubes OS should stick to GNU+Linux standards of naming. Dolphin, Partition manager, command-line tools like dd do support binary notation.

The solution you'd like

The usage of MiB and other binary prefixes for sizes everywhere (in GUI and qubes commandl-ine tools) can make everything clear and consistent.
The usage of MB, especially as 10^6 should be left for sellers of RAM, HDD and SSD to deceive their buyers only.

The value to a user, and who that user might be

No misunderstanding and misinterpretation, consistent values in Qubes OS GUI and tools.

@jamke jamke added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. labels Nov 17, 2022
@andrewdavidwong andrewdavidwong added help wanted This issue will probably not get done in a timely fashion without help from community contributors. C: other P: minor Priority: minor. The lowest priority, below "default." good first issue This is a recommended issue for first-time contributors. and removed P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. labels Nov 18, 2022
@andrewdavidwong andrewdavidwong added this to the Non-release milestone Nov 18, 2022
@andrewdavidwong andrewdavidwong removed this from the Non-release milestone Aug 13, 2023
alimirjamali added a commit to alimirjamali/qubes-manager that referenced this issue Aug 9, 2024
alimirjamali added a commit to alimirjamali/qubes-manager that referenced this issue Aug 9, 2024
@alimirjamali
Copy link

PR Submitted

Review priority: low

p.s. This is for Qube Manager only. If there is any other occurrence of MB or GB in other GUI (or CLI) tools, please report them by replying to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: other good first issue This is a recommended issue for first-time contributors. help wanted This issue will probably not get done in a timely fashion without help from community contributors. P: minor Priority: minor. The lowest priority, below "default." pr submitted A pull request has been submitted for this issue. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants