![]() 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. No manual upload or download needed Support for SSH (Secure Shell) and FTP (File Transfer Protocol) servers. Work with your files using your favorite Mac OS X applications directly. I’m looking at Apple’s Deprecated Kernel Extensions and System Extension Alternatives article, as well as macfuse requires a kernel extension to work. Macfusion brings servers from across the internet directly to your Mac's desktop Mount files and documents as a 'Volume' in the Mac OS X Finder. 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. Also: I was offering to turn those code contributions back to you, closed-source, not release them myself. 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. 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. 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? I accepted that this would prevent others from contributing code to the closed source components. 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. Uninstalled WorkDocs Drive and also deleted all references to macFUSE from the various locations on my Mac boot drive, rebooted. ![]() Just upgraded to Monterey, Mac OSX Version 12.0.1, and after the final reboot, I see many macFUSE errors generated by WorkDocs Drive. Back when macFUSE was still open source, I was looking for help, but there were no regular contributors besides me. macfuse 4.2.1 works on Big Sur and Monterey Have a question about this project Sign up for a free GitHub account to open an issue and contact its maintainers and the community. I was using WorkDocs Drive under Big Sur without any issues. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |