On the other hand, libfuse and its many ports provide a portable high-level interface that may be implemented on a system without a "FUSE" facility. Īs the kernel-userspace protocol of FUSE is versioned and public, a programmer can choose to use a different piece of code in place of libfuse and still communicate with the kernel's FUSE facilities. A break in libfuse history is libfuse3, which includes some incompatible improvements in the interface and performance, compared to the older libfuse2 now under maintenance mode. The exception is the FUSE fork for macOS, OSXFUSE, which has too many differences for sharing a library. This is possible because the kernel FUSE reports its own "feature levels", or versions. The userspace side of FUSE, the libfuse library, generally followed the pace of Linux kernel development while maintaining "best effort" compatibility with BSD descendants. įUSE was merged into the mainstream Linux kernel tree in kernel version 2.6.14. An ISC-licensed re-implementation by Sylvestre Gallon was released in March 2013, and incorporated into OpenBSD in June 2013. It superseded Linux Userland Filesystem, and provided a translational interface using lufis in libfuse1.įUSE was originally released under the terms of the GNU General Public License and the GNU Lesser General Public License, later also reimplemented as part of the FreeBSD base system and released under the terms of Simplified BSD license. The FUSE system was originally part of AVFS ( A Virtual Filesystem), a filesystem implementation heavily influenced by the translator concept of the GNU Hurd. 3.4 Remote/distributed file system clients.
0 kommentar(er)
