-
Notifications
You must be signed in to change notification settings - Fork 117
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
ntfs support #42
Comments
This would be great. Will take a look soon. squashfs and ext4 still are in the works... |
I have a read-only NTFS implementation brewing along which even has a limited write support (= filesystem generation). By limited I mean not implementing journaling: write-once, i.e. what formatting a partition does + allows overlaying files at write-time. I'm not planning on implementing writes via journaling, but if someone wants to implement that I think I have a solid base by supporting marshaling NTFS data structures in both directions (not just reading). My implementation is of some quality, it has in-memory block device shim for testing purposes and once I've generated the FS in-memory, there's "chkdsk"-like test suite that validates the testing in-memory block device's content from the read layer. I even have tests validating the MFT mirror. I'll keep you posted once I make the repo public. |
That generally is my approach as well. The qcow2 implementation in process basically treats it like a regular filesystem, doing writes. It doesn't bother with multiple layers and backing files. Some day, perhaps, but the vast majority of use cases that I see simply want to write and be done. |
github.com/Velocidex/go-ntfs
github.com/gentlemanautomaton/ntfs
Thank you
The text was updated successfully, but these errors were encountered: