-
Notifications
You must be signed in to change notification settings - Fork 245
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
Feature request: global option to print offsets and such in hexadecimal #749
Comments
Do you have suggestion for the option name and format? I think there would need to be list of value categories where this applies, ie. not for inode numbers. I don't know how much flexible the format should be, we can do a preselected list of values where hex format would make sense. If this there's a need to make it more flexible (like adding exceptions for certain types) then the specifier can be enhanced. Possible format: |
For reference, I find these notations most useful (in bees and some other tools I developed):
I didn't find lengths in hex to be very useful compared to the range notation. Range notation in hex shows clearly whether the end of the range is page-aligned regardless of the start of the range. It's also more convenient when overlapping matching ends of ranges. For device offsets I find units of 1024M with 3 fixed decimal places are useful. 1 GiB-aligned dev_extents are "xxx.001" in that notation. That's really obscure, though, and I don't know of a btrfs-progs tool that even outputs that information other than |
I would be quite happy with what Zygo suggested and don't have very much to add. Range notation would be especially handy! A simple option like |
No description provided.
The text was updated successfully, but these errors were encountered: