You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was only recently made aware of this library. Fsspec has some similar concerns, but is primarily used for interacting with remote storage systems, whereas most of the FS-like targets here are local file containers. Would you like to provide a shim such that fsspec.filesystem or fsspec.open can deal with a dissect target filesystem type? It could have a benefit to you, maybe opening a filesystem container file in a remote store.
I am also interested in the FUSE integration. fsspec also has this, but it is flaky, experimental and rarely used. Perhaps the solution here is more robust, and all fsspec filesystem types could be exposed.
The text was updated successfully, but these errors were encountered:
Hi @martindurant, thanks for reaching out! Apologies for the delayed response, I also saw the other thread where Dissect was mentioned and wanted to give an in-depth reply there, but some things came up and I just couldn't get around to it yet. When I have some more time I'd still like to elaborate some of our decisions and goals in further detail there.
To give a short response, this looks interesting to us and something we'd be interested in exploring. Could you perhaps give a short overview of the necessary tasks or some API references so we can make an estimate on how much work this would be?
FYI, our FUSE implementation isn't flawless (or particularly fast), but it does get used very heavily and seems to be pretty stable overall.
I was only recently made aware of this library. Fsspec has some similar concerns, but is primarily used for interacting with remote storage systems, whereas most of the FS-like targets here are local file containers. Would you like to provide a shim such that fsspec.filesystem or fsspec.open can deal with a dissect target filesystem type? It could have a benefit to you, maybe opening a filesystem container file in a remote store.
I am also interested in the FUSE integration. fsspec also has this, but it is flaky, experimental and rarely used. Perhaps the solution here is more robust, and all fsspec filesystem types could be exposed.
The text was updated successfully, but these errors were encountered: