5.0.5 installs v. 5.0.4? #1093
-
|
I'm trying out the macOS 26 beta. I used the 5.0.5 .dmg to install macfuse since 5.0.x are the only ones that run on macOS 26. In System preferences. the perf pane says I'm using 5.0.5. However: % defaults read /Library/Filesystems/macfuse.fs/Contents/Extensions/26/macfuse.kext/Contents/Info CFBundleVersion Executing: /usr/bin/kmutil showloaded So I extracted the contents of the installer and checked to see what version it installs: % defaults read /tmp/macfuse_extract/Core.pkg/Payload/Library/Filesystems/macfuse.fs/Contents/Extensions/26/macfuse.kext/Contents/Info CFBundleVersion I have a feeling something is off. plus, I'm getting write fails (bad address) when using fuse mounted volumes. I couldn't find any discussions on this. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Since macFUSE 4.9.0 the kernel extension version is decoupled from the release version. This avoids unnecessary reboots. See https://github.com/macfuse/macfuse/releases/tag/macfuse-4.9.0 The 5.0.5 release contains kernel extensions version 5.0.4. There have been no changes to the kernel code in 5.0.5.
Please raise the issue with the developer of the file system you are using. In case you think macFUSE is to blame for the fails, please open an issue (https://github.com/macfuse/macfuse/issues) and provide as much information as possible including (ideally) step by step instructions allowing me to reproduce the issue. |
Beta Was this translation helpful? Give feedback.
Since macFUSE 4.9.0 the kernel extension version is decoupled from the release version. This avoids unnecessary reboots. See https://github.com/macfuse/macfuse/releases/tag/macfuse-4.9.0
The 5.0.5 release contains kernel extensions version 5.0.4. There have been no changes to the kernel code in 5.0.5.
Please raise the issue with the developer of the file system you are using. In case you think macFUSE is to blame for the fails, please open an issue (https://github.com/macfuse/macfuse/issues) and provide as much information as possible including (ideally) step by step instructions allowing me to reproduce the issue.