The MacFUSE project has been updated to version 1.5 and brings with it more support for Leopard as well as many bug fixes.
MacFUSE is an Open Source FUSE-Compliant File System Implementation Mechanism for Mac OS X. MacFUSE implements a mechanism that makes it possible to implement a fully functional file system in a user-space program on Mac OS X (10.4 and above). It aims to be API-compliant with the FUSE (Filesystem in USErspace) mechanism that originated on Linux. Therefore, many existing FUSE file systems become readily usable on Mac OS X. The core of MacFUSE is in a dynamically loadable kernel extension.
Although MacFUSE has a completely different kernel-level implementation from Linux FUSE, it supports the FUSE specification well enough that many popular FUSE file systems can be easily compiled and work on Mac OS X–often out of the box. Examples of file systems that work and have been tested (to varying degrees) include sshfs, ntfs-3g (read/write NTFS), ftpfs (read/write FTP), wdfs (WebDAV), cryptofs, encfs, bindfs, unionfs, beaglefs (yes, including the entire Beagle paraphernalia), and so on.
Changes and Feature Additions in MacFUSE 1.5 Core Binary Releases
• Bugfix: Fixed an exit(3) call that should have been _exit(3). Could cause tear-down issues for certain file systems.
• Feature: If a user file system becomes dead or unreachable (for example, if the daemon crashed), MacFUSE will report -1 as the file system subtype (the f_fssubtype field of struct statfs64 and the f_reserved1 field of struct statfs.) The MacFUSE file system property list files now identify subtype -1 as the “dead” file system.
• Feature: 10.5: Experimental support for select(2) on the user-kernel device. Must be explicitly enabled at kernel extension compile time through M_MACFUSE_ENABLE_DSELECT.
• Feature: 10.5: Added support for file flags (see chflags(2)). Currently, a user file system can only provide these flags for reading. Support for setting these flags is there, but not enabled because doing so will extend (”break”) the existing FUSE API and is a more disruptive change–it will require all existing file systems to be recompiled. This change will be clubbed together with other disruptive changes at some point in the near future.
• Update: 10.5: User-space library now based on FUSE library version 2.7.3.
For more information head on over to the MacFUSE Project.