![]() ![]() Those that are quickest and simplest to calculate are normally most prone to collisions, in which two different files have the same checksum. ![]() There’s a wide choice of different checksums and hashes which can be used for this. For macOS native file systems, they’re an add-on for the user. When these are made by the file system, they’re effortless for the user, but currently that isn’t an option with either HFS+ or APFS. Most techniques of checking and maintaining file integrity start with making checksums, hashes or ‘digests’ of each file to be protected. This article looks at an alternative, using my free family of utilities, including Dintch, which has just been updated. Ideally, we could use a file system that includes integrity checks, such as ZFS or Btrfs, but those are only readily available on external systems such as NAS, and not native to macOS. While backing them up in depth should ensure that no matter what happens, we can always find a copy, how can we tell whether it’s intact, or has been damaged or corrupted? ![]() All of us have important files we don’t want to lose.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |