Tv

`FUSE_COPY_FILE_RANGE` was added in protocol 7.28, we're currently stuck around 7.12 because last I looked, OSXFUSE didn't support 7.20 (https://github.com/osxfuse/osxfuse/issues/155) and then both the OSXFUSE upstream and Apple turned hostile...

Need to check what FreeBSD is up to, but yes, we should be able to bring the protocol up now a lot more easily than writing lots of conditionals and...

I like the general idea, but you really shouldn't be running as root (or CAP_SYS_ADMIN either). I'd like to see a complete story about that; go is not great at...

Looks like the kernel removes it intentionally: https://github.com/torvalds/linux/blob/cb690f5238d71f543f4ce874aa59237cf53a877c/fs/fuse/inode.c#L201-L208 See also https://pkg.go.dev/bazil.org/fuse#DefaultPermissions

Oh, except on top of that we might be missing sticky bit handling where we convert to Go `os.FileMode`. Testing...

While we would fail to convert the incoming mode to include Go `os.ModeSticky`, I have yet to see the sticky bit in input, even with `DefaultPermissions` and running as root....

So I wasn't seeing a sticky bit in input because I was mixing unix mode bits and Go's shuffling of what bit means what, and giving garbage input to `os.Chmod`....

\ More serious status update: lots of life changes, big refactor that is not quite ready and is proving very hard to break into smaller changes. Expect a phoenix resurrection...

I think the next step is to add tests for GenerateInode, it seems I never got around to do that.

I wrote a unit test for `GenerateInode` in commit ac2adf203b6787dd54f98a7d05456aad3444bbd6 and it seems to work just fine. Please provide more information, ideally a small filesystem implementation that demonstrates the issue.