fixes around fat32 and lfn support #16
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a drive-by PR.
I was investigating a corrupted vfat based system today and needed something to poke programmatically at the broken image. Your library was exactly the right tool (modulo some small issues that I had to tweak, see below), many thanks for it!
The image was fat32 so I added (hacky) support to get the root directory for fat32. I also fixed some issues in the lfn (long-file-name) reading. For my purposes this works well enough and I just wanted to share my fixes as they may be useful to other.
Cheers,
Michael