Great news in the MacOSX developer camp. Most recently, the release of the project
Fuse4X - port Fuse under MacOSX.
Traditionally, file systems are developed as modules of the operating system kernel, but unfortunately this has its drawbacks:
- Kernel-level development is more complicated. The de-reference of the wrong pointer results in a BSOD, the deadlock in the kernel can lead to the system hanging, and there are no normal debugging tools for the kernel modules.
- API of various kernels is incompatible. A module written under Linux will not work under MacOSX and vice versa.
- Installing a kernel module requires administrative privileges.
These problems and is intended to solve the
Fuse . Initially, this project was developed under Linux, but now it has been ported to other operating systems, in particular, under MacOSX.
Fuse4X is a fork and continuation of the
MacFUSE project. You will surely ask “What's wrong with MacFUSE”? The MacFUSE project started in 2007 and, thanks to its usefulness, quickly became popular - macfuse is used in dozens of macosx applications. But in 2008, the author (Amit Singh) stopped developing the project and switched to the commercial version of MacFUSE. Moreover, the author refuses to transfer the project to someone else. The latest release of MacFUSE was released in 2008, does not support 10.6 and 64 bit kernels. In general, this project is dead.
')
Fuse4X took over the baton from MacFUSE and continues its development. Fuse4X works fine under 10.6, on 64 bit cores. Fuse4X is much more compatible with Fuse under Linux - this is especially important for developers of cross-platform applications.
In general, if you need to present any resource as a file system - know that Fuse4X is for you.
Install Fuse4X , use it, create your own file systems, study the
source code of Fuse4X and send your patches.