Atlas (Rubrik backup software): Immutable, distributed filesystem used by Rubrik Cloud Data Management data protection applications.Archive filesystems may also perform this taskįUSE filesystems can expose the contents of archives or backup sets without having to first extract them.FuseCompress, gzipfs, Fuse-ZIP, CompFUSEd: Compressed virtual filesystems.The current version of retro-fuse supports mounting filesystems created by Fifth, Sixth and Seventh Edition of Research Unix from BTL, as well as 2.9BSD and 2.11BSD based systems.įUSE filesystems can create a view of an underlying file system, transforming the files in some way. retro-fuse: retro-fuse is a user-space filesystem that provides a way to mount filesystems created by ancient Unix systems on modern OSes.NTFS-3G and Captive NTFS, allowing access to NTFS filesystems.Linear Tape File System: Allows files stored on magnetic tape to be accessed in a similar fashion to those on disk or removable flash drives.In principle, any resource available to a FUSE implementation can be exported as a file system.Īpplications On-disk file systems Ĭonventional on-disk file systems can be implemented in user space with FUSE, e.g. They act as a view or translation of an existing file system or storage device. Unlike traditional file systems that essentially work with data on mass storage, virtual filesystems don't actually store data themselves. Unmounting a FUSE-based file system with the fusermount commandįUSE is particularly useful for writing virtual file systems. 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. He said, "They will probably laugh at me, for having little to no clue on fuse." but I thought it's worth sharing one person's observations in order to open a dialog. It is our sincere hope that things have changed, or are changing, and we're excited to see that FUSE development has resumed on Mac OS. It is suspected that if he had gotten anywhere with it, MacFUSE might not have been robust enough to have supported ZFS. In addition to not having enough time to fix everything in the world, he found that zfs-fuse just wouldn't compile on the 2010 release of MacFUSE. Hey as a huge coincidence, one of the MacZFS engineers named Bjoern has just published some notes which he had written down a long long time ago, maybe years ago, on a piece of paper, on the subject of porting MacZFS to MacFUSE. I'm not a programmer, but I authored the FAQ and much of the rest, so please let me know if I can help. In a perfect world, if people have enough time and whatnot, we would like to collaborate with FUSE at least for the purpose of debugging in userspace. I don't know the answer to your question but I'm hailing from the MacZFS camp at which has a native kernel implementation of onnv_74 (zpool v8, zfs v2).
0 Comments
Leave a Reply. |