-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS FUSE-T support #273
Comments
Ya, happy to merge a PR, if it's a simple change |
FUSE-T is a C library implementing the same C API as |
It seems like there was a PR for this -- #225 -- but it was rejected. I'm not sure whether it ever worked or whether the reason was the closed nature of FUSE-T or whether it was something else. |
Oh, I see that fuser has support for the C libfuse library as an optional feature. I didn't realize that before. (Maintaining that moral-equivalent of ifdef hell can't be fun.) |
Thankfully they will not be required soon, as macOS Sequoia (15+) adds an official API for user-space file systems called FSKit: https://developer.apple.com/documentation/fskit/ Announcement article: https://eclecticlight.co/2024/06/26/how-file-systems-can-change-in-sequoia-with-fskit/ |
as kext support on macOS is effectively history would you consider supporting alternatives like FUSE-T? On all new macs (ARM based) running kext requires lowering all system security - and soon will be gone for good given Apple dev announcements (no 3rd party kernel extensions).
Good news is that people are already working on alternatives:
https://www.fuse-t.org/
"It implements its own userspace server that converts between FUSE protocol and NFS calls and let macOS mount NFS volume instead of a kernel filesystem"
and is fuse API compatible so usually is very easy replacement (just linking to fuse-t libs instead of macfuse)
Info for developers - https://github.com/macos-fuse-t/fuse-t/wiki
"In general, the code that worked with osxfuse should work as-is without any changes except linking to a new fuse-t library provided in the installation package."
The text was updated successfully, but these errors were encountered: