Han-Wen Nienhuys
Han-Wen Nienhuys
AFAIK, FUSE doesn't exist on windows. Why would you try to build it on windows?
I don't use windows. If you can get go-fuse to work with dokany or winfsp, I'm happy to review contributions.
if possible, I'd prefer a gerrithub review.
> Also, memnodefs is completely in-memory, no? the file contents are backed by a normal filesystem. It is just the tree and metadata that are in-memory.
See https://github.com/hanwen/go-fuse/issues/460 . I have tried to make the opendir/readdir API easy to use, but the result is messy if you want to do more than opendir/readdir/closedir. OpenDir doesn't return...
thanks, very insightful. You say > So a naive FUSENFSv4 bridge would most likely end up leaking nodes a lot. doesnt the semantics of NFS mean that an NFS server...
can you show an excerpt of the debug log for when this goes wrong? or, even better a test case?
see https://review.gerrithub.io/c/hanwen/go-fuse/+/1194779
https://github.com/hanwen/go-fuse/commit/1e27f6dd72c5593f8ae054b3ae9b8927c49a95e7
I should probably delete newunionfs. I wanted to write the old unionfs on top of the new `fs` api, but since I have dropped `unionfs`, the new version can go...