it would be useful to have an option to specify offset for fat32 bootable images that could be inspected right a way without a need to create an intermediate file using dd like

dd if=boot.img of=boot_shifted.img skip=2048

It seems that fsck is using byte "0x41" (FAT32) or "0x25" (FAT16) as as the containing byte of this bit.

However, the FAT specification indicates that the first two clusters of a FAT are reserved for information which includes this dirty bit (notably, not within the boot sector). It also mentions that byte 0x41/0x25 is "BS_Reserved1", which "is "Reserved (used by Windows NT). Code that formats FA

Is your feature request related to a problem? Please describe.
Currently fat-cli uses the cobra cli framework and uses unix style flags, but fatd uses just the plain "flags" package and some custom parsing. This means that there is some code duplication for common flags (which may be unavoidable in some places anyway) but mainly this creates an unfortunate user experience when switching b

We need to add some sections to the documentation:

• Why we wrote this tool, why should our program be used, analysis of existing tools...
• Use case of our tool
  • Maybe just describing a brief scenario where one could use this tool
  • Mention that no encryption is applied to the hidden data, so the user is responsible for that.
• ~~Document create_testfs.sh includi