AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Osxfuse vs macfuse12/28/2023 The macFUSE GitHub organization is (in some regards) more current than the osxfuse GitHub organization. That's why osxfuse has been rebranded to macFUSE. The other problem is one of branding/terminology:.The modifications are kept to the bare minimum to make merging in upstream changes less painful. The repository contains a minimally patched version of libfuse that runs on macOS. The README.md file in contains only Linux-specific information that (for the most part) do not apply to FUSE on macOS. macFUSE-specific issues should be reported to the macFUSE project. General libfuse issues should be reported to the upstream project. If you are the same people, or at least connected, could you please update that info, so that Mac specific issues land where they should, so supposedly here at įUSE on Linux and FUSE on macOS are separate projects.This rarely leaves any time to look into sshfs-specific issues. sshfs should gracefully unmount the volume in case the connection is lost or cannot be established in the first place. I think, the best starting point for investigating the issue would be the error handling in sshfs. The issue you are running into is most likely related to sshfs. Please report any bugs on the GitHub issue tracker at I reported and meanwhile closed a Mac FUSE related issue at the wrong place due to misinformation in the README.md at which states: If that is not adequate or possible then please at least make sure that the homepages/readme.md of the respective repos point out clearly to newcoming users in their README.md what is hosted/handled where, and where users should direct their feedback/efforts to.From that perspective ideally macfuse should be the main place of activity.So newcomers may suspect "macfuse" to be the more current or more adequate repo than "osxfuse" which refers to a name not used by Apple anymore.Apple rebranded its OS from "Mac OS X" to "macOS" in 2016.The other problem is one of branding/terminology: If you are the same people, or at least connected, could you please update that info, so that Mac specific issues land where they should, so supposedly here at Please report any bugs on the GitHub issue tracker at Inquiries I reported and meanwhile closed a Mac FUSE related issue at the wrong place due to misinformation in the README.md
0 Comments
Read More
Leave a Reply. |