3 ms·
According to the MacFUSE author, their specific approach is not actually undocumented: > Apple has put it in an umbrella called "unsupported" (in the kernel in
by ranger_danger 3y ago
According to the MacFUSE author, their specific approach is not actually undocumented:
> Apple has put it in an umbrella called "unsupported" (in the kernel interfaces section) ... either Apple will not take this interface away, and if they do, it will be to provide a better interface
http://preserve.mactech.com/articles/mactech/Vol.23/23.03/MacFUSE-SinghInterview/index.html http://preserve.mactech.com/articles/mactech/Vol.23/23.03/Ma...
- skissane 3y agoYes, that’s not what I’m talking about though MacFUSE uses the kernel mode VFS API I’m talking about the undocumented user mode filesystem LiveFS/UserFS/com.apple.filesystems.lifs API which was added in Monterey (macOS 12), and since Ventura (macOS 13) is used to implement the OOTB FAT and exFAT filesystem support. Using that requires private entitlements (e.g. com.apple.private.LiveFS.connection) which Apple (thus far) won’t give to anyone else
- ranger_danger 3y agoWhat about the File Provider API?
- skissane 3y agoIt is designed for the cloud storage use case (Dropbox, Google Drive, etc) - it creates local copies of files and synchs them with remote ones. Not what you want to do in the general case.
- skissane 3y agoI take it from the downvotes people think what I said is factually wrong? If that's the case, I wish someone would point out where I've got it wrong instead of just silently downvoting