fuser advertises every filesystem as case-insensitive on macOS (src/lib.rs#L120-L126). Nothing in the stack needs this flag: macOS and macFUSE fully support case-sensitive filesystems (verified on macFUSE 5.1.2).
The request is a leftover from 2013, when the crate assumed "our filesystems are usually case-insensitive" 7c1fa33, and the code has carried a TODO since 2fd65cf.
Note that this is a backward-incompatible change: users that relied on this behavior need to explicitly request it with
KernelConfig::add_capabilities(InitFlags::FUSE_CASE_INSENSITIVE) in Filesystem::init. I think it's low risk, and given fuser is pre 1.0, it's cleaner to just drop the flag from the default list than to add a mechanism to un-request flags.
fuser advertises every filesystem as case-insensitive on macOS (src/lib.rs#L120-L126). Nothing in the stack needs this flag: macOS and macFUSE fully support case-sensitive filesystems (verified on macFUSE 5.1.2).
The request is a leftover from 2013, when the crate assumed "our filesystems are usually case-insensitive" 7c1fa33, and the code has carried a TODO since 2fd65cf.
Note that this is a backward-incompatible change: users that relied on this behavior need to explicitly request it with
KernelConfig::add_capabilities(InitFlags::FUSE_CASE_INSENSITIVE)inFilesystem::init. I think it's low risk, and given fuser is pre 1.0, it's cleaner to just drop the flag from the default list than to add a mechanism to un-request flags.