FUSE
Filesystem in Userspace (FUSE) is a mechanism for Unix-like operating systems that lets non-privileged users create their own file systems without editing kernel code. This is achieved by running file system code in user space, while the FUSE kernel module provides only a "bridge" to the actual kernel interfaces.
Unmounting
FUSE filesystems can be unmounted using fusermount3(1) provided by fuse3 or using fusermount(1) provided by fuse2. E.g.:
$ fusermount3 -u mountpoint
List of FUSE filesystems
- adbfs — Mount an Android device connected via USB.
- apfs-fuse — FUSE driver for APFS (Apple File System).
- astreamfs — A(synchronous) Stream(ing) (fuse) F(ile)S(ystem).
- CurlFtpFS — Filesystem for accessing FTP hosts based on FUSE and libcurl.
- GDriveFS — Innovative FUSE wrapper for Google Drive.
- NTFS-3G — NTFS driver with extended capabilities.
- SSHFS — FUSE-based filesystem client for mounting directories over SSH.
gollark: No, I mean it would be hard to do in the various open source OSes.
gollark: > Maybe you've never thought about this, but if there are 100 devs working for free you'd only need to hire 50 devs to compromise all their code.That's, um, still quite a lot given the large amounts of developers involved, and code review exists, and this kind of conspiracy could *never* stay secret for very long, and if you have an obvious backdoor obvious people are fairly likely to look at it and notice.
gollark: Those are increasingly not working because of better security in stuff, which is probably good.
gollark: There is actually a wikipedia page for that.
gollark: I mean, I got a letter back from some government official, having sent an *email* the week before, which was only tangentially related to what I actually said.
This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.