Is this going to impact macFUSE? Is there a risk that macFUSE 4.2. ZDNet | Apple deprecating macOS kernel extensions (KEXTs) is a great win for security, and it sounds like the message is that Apple wants to phase out support for kernel extensions, and have developers migrate to System extensions instead. I’m looking at Apple’s Deprecated Kernel Extensions and System Extension Alternatives article, as well as In case you run into any issues on macOS 12, please open a new ticket.Ĭan you please comment on the status of macFUSE’s use of kernel extensions (kexts) in macOS 12 Monterey? The new macFUSE 4.2.0 release adds experimental support for macOS 12. macOS monterey 12.5.1 apple M1 chip with macFuse 4.4.1 mount and unmount.
#Macfuse for monterey code
Also: I was offering to turn those code contributions back to you, closed-source, not release them myself. macFUSE osxfuse: FUSE extends macOS by adding support for user space file.
I don't disagree with you looking to make a living off your work, I'm just asking you to let me fix it myself if you can't do so in a timely fashion, but you've done so, so it's a moot point. macfuse requires a kernel extension to work.
#Macfuse for monterey plus
This is simply the latest iteration with MacFUSE (4.2.4) on macOS Monterey (12.2.1) on an Apple M1 (Max) chipset, plus a bit on using it with sshfs. system requirements were considerably stricter than those for macOS Monterey. It seems that each time Apple releases a new OS version, there are challenges in getting MacFuse installed. The main motivation for this project is to replace macfuse that implements. As you've moved to a for-profit model, I'd think it goes without saying I'm not going to be taking on any financial strain the project maintainer was not willing to. MacFUSE, a FUSE module for macOS, has been around in various forms for quite some time. I'm sorry, I believe you misunderstood me, I was only offering help as far as updating osxfuse to run on macOS Monterey, not making a commitment to help out long-term. the open source components of macFUSE, if you are interested. However, there are areas you could help with, e.g. I will not release the source code of the kernel extension and risk the project's funding in hope that it might turn out differently this time. What happens after your off time ends, when you have less time to spare? It seems that each time Apple releases a new OS version, there are challenges in getting MacFuse installed.
I accepted that this would prevent others from contributing code to the closed source components. MacFUSE, a FUSE module for macOS, has been around in various forms for quite some time. Long story short, the only remaining option was going closed source to improve the project's funding so that I could spend more time working on it. Back when macFUSE was still open source, I was looking for help, but there were no regular contributors besides me. You are taking my two-year-old comment out of context. Soooo, I'm guessing the whole "oh if another developer experienced in kext development would help I'd be glad but nobody will" is a load of crap?
0 kommentar(er)
