12/12/2023 0 Comments Macfuse remove![]() ![]() If installing the library under the same name meant that existing file systems would continue to work, that would certainly be desirable. But it occurs to me that that does mean migrating from macfuse to fuse4x would require rebuilding all installed filesystems just to link them against a new library. It doesn't bother me so much that ports will need to know to link with -lfuse4x instead of -lfuse, even though there are a couple that will need to be patched. For one, the benefit is illusory: macfuse and fuse4x won't actually be able to coexist - at least not in MacPorts, and probably not with a standalone-installed version either - because both of them want to install $prefix/include/fuse.h in the same place. I contemplated this one some more today and I'm undecided about whether this is a good idea. The idea is to make fuse4x and macfuse coexist together on the same computer. Replying to noticed the library installs as libfuse4x.dylib rather than libfuse Please try 'pu' branch and let me know what issues are left. That may have been introduced in 10.6? Seems like this is the biggest problem. Please try possible fix in 'pu' branch.įuse_internal.c got a missing symbol on vnode_isrecycled. sounds weird this macros should be defined on 10.5. Not sure how much it matters that it actually corresponds to the page size, anyway. It's probably defined in some header file, but I'm not sure which one. I uploaded it to 'pu' branch.įuse_params.h has PAGE_SIZE undefined. I set KPI version to 9.0.0 (the one used on 10.5). The kext's ist needs different version numbers for its OSBundleLibraries dependencies Load_fuse4x uses the C API for loading kexts that doesn't exist on 10.5. The fix for fuse_unmount_compat22() is in master already. The change should be merged to master soon. I also made kext messages more helpful for this error. I don't understand why the code appears to be the same and the sysctls have the same defaults. What I'm puzzled by is that this works fine with MacFUSE (I just verified this). ![]() After much debugging, I realized the problem was that bindfs uses -o allow_user by default, and the kext rejects that with EPERM unless the fuse_allow_other sysctl is set or the user is a member of the fuse admin group. No, that's not it (and dmesg was unhelpful). Also check /var/log/system.log - it should contain more info. Make sure that /private/tmp/foo is owned by the user. I moved libsem (semaphores implementation based on pthreads) from macfuse to sshfs. Is fixing the usage of sysv semaphores the only change in your version of sshfs? Replying to to builds but spends all of its time spinning in sem_wait, presumably because of the issue you found whereįuse4X has its own sshfs port that solves all these problems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |