3 ms·

hexedit (included in debian/ubuntu) and dd (included in everything) seem to cover both large files and scriptability quite well

• resiliware 6y ago
  hexedit, as with most traditional hex editors, prints file offsets as 32 bits. So for offsets > 4GiB+, either the editor doesn't show the offset correctly, or it reformats the screen to handle it and has inconsistent widths within output. You are of course correct that dd provides the basics. However my goal with hexpeek was to create a more powerful and user-friendly tool than relying on dd. For example, how do you insert one byte in the middle of huge file with dd? Yes it can be done with multiple commands, but with hexpeek it is one command.
• Traster 6y ago
  Yes, I was confused by this too - because my only experience of using hex editors was hexediting an executable (definitely not to remove some DRM), hexedit was very capable and the executable wasn't exactly small.
  • resiliware 6y ago
    My lower bound for huge files is 4GiB. The actual use case that started the development of hexpeek was trying to surgically inspect and modify disparate parts of a 100GiB file. I'm not sure if your executable was that large.