Bill Zissimopoulos

I am glad this worked for you. I do think that this should be considered a bug and that there should possibly be a second check in the kernel after...

@alfaunits File/Folder access should work correctly with unmodified MEMFS/PTFS. If it does not you have found a bug. Access permissions in a MEMFS file system depend on how you launch...

Good catch. I agree that linking with Windows system DLLs and/or system/language runtimes (such as MSVCRT, golang runtime, etc.) should be allowed. Do you have any suggestion for wording that...

The WinFsp kernel protocol requires that the file size is correctly reported upon completion of a `Write` request. The WinFsp-FUSE layer (i.e. the FUSE layer of WinFsp) needs to perform...

Yes, `FileInfoTimeout=-1` instructs the FSD (File System Driver) to enable the kernel data cache. This does the following: - Ensures that kernel mode metadata caches (e.g. file information such as...

> Lastly, even FileInfoTimeout=-1 works as expected, is there a way to manually flush cache to underling file system. We implement in a stackable file system way, so we want...

I will look into this more closely, but I believe the reason for this problem is a combination of the following: - The drive Z: is created in the namespace...

I can confirm the problem when mounting as a disk file system. However it seems to work correctly when mounting as a network file system (using the `-u` switch). I...

@sganis thanks for the enhancement request. Implementing this should be relatively easy as we would just wrap the equivalent operation in FUSE2. The bigger issue is that this would introduce...

@mheinzler > Do I understand correctly that the main issue for extending fuse3_operations would be breaking future compatibility with libfuse's fuse_operations? You are correct. I would not mind adding `chflags`,...