-
Notifications
You must be signed in to change notification settings - Fork 57
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
Allow mounting of merged filesystems #239
Comments
Something like this isn't going to work unless there's either a major change to the file system format, or you're willing to not only explicitly provide the offset, but also the length of the file system. A DwarFS image is just a sequence of blocks; there are no explicit begin / end markers, although DwarFS assumes that the last block might be a section index. However, when simply concatenating multiple DwarFS images, there's no way to tell (other than by heuristics) where one image ends and another one starts. I'm not going to add any such heuristics, because they would very likely conflict with future extensions, such as being able to append/update DwarFS images. So, the only option would be to explicitly provide offset/length of the image within the file. |
To provide the length of the image would be no problem for my use case, is there an option for it? |
No, there's no such option yet. It should be fairly simple to add, though. |
Please try the experimental/image-size branch. You should be able to do something like:
Let me know if that works for you and I'll pull the change in for the next release. (I've only written unit tests, but didn't actually test the FUSE driver (yet) — so definitely let me know if it's not working as expected.) |
@mhx thanks for implementing this! I just finished compiling and got the novel option in the help menu |
Greetings!
I would like to request a feature to mount merged filesystems, i.e.:
Currently this is not possible, when trying to mount the
folder.dwarfs
file I get the error:This is for both
dwarfs
commands, with and without the offset.The text was updated successfully, but these errors were encountered: