disabled "ˆl–ßi~” Še¶¥8 Y¸Ûw☴oÁ ƒh¹À¿disabled #ˆl–ß=¿J Å!®Å‰@?p@¸ÓÊbÑ¿Â „ aÁÀ;This was generated on 2006/10/17 from http://sourceforge.net/apps/mediawiki/fuse/index.php?title=FAQ For an up to date version please see the above page. You can also add new entries there. General ======= How can I umount a filesystem? ------------------------------ FUSE filesystems can be unmounted either with: umount mountpoint or fusermount -u mountpoint The later does not need root privileges if the filesystem was mounted by the user doing the unmounting. What's the difference between FUSE and LUFS? -------------------------------------------- The main difference between them is that in LUFS the filesystem is a shared object (.so) which is loaded by lufsmount, and in FUSE the filesystem is a separate executable, which uses the fuse library. The actual API is very similar, and there's a translator, that can load LUFS modules and run them using the FUSE kernel module (see the lufis package on the FUSE page). Another difference is that LUFS does some caching of directories and file attributes. FUSE does not do this, so it provides a 'thinner' interface. By now LUFS development seems to have completely ceased. Why is it called FUSE? There's a ZX Spectrum emulator called Fuse too. ---------------------------------------------------------------------- At the time of christening it, the author of FUSE (the filesystem) hadn't heard of Fuse (the Speccy emulator). Which is ironic, since he knew Philip Kendall, the author of that other Fuse from earlier times. Btw. the author of FUSE (the filesystem) also created a Speccy emulator called Spectemu. The name wanted to be a clever acronym for "Filesystem in USErspace", but it turned out to be an unfortunate choice. The author has since vowed never to name a project after a common term, not even anything found more than a handful of times on Google. Is it possible to mount a fuse filesystem from fstab? ----------------------------------------------------- Yes, from version 2.4.0 this is possible. The filesystem must adhere to some rules about command line options to be able to work this way. Here's an example of mounting an sshfs filesystem: sshfs#user@host:/ /mnt/host fuse defaults 0 0 The mounting is performed by the /sbin/mount.fuse helper script. In this example the FUSE-linked binary must be called sshfs and must reside somewhere in $PATH. Licensing issues ~~~~~~~~~~~~~~~~ Under what license is FUSE released? ------------------------------------ The kernel part is released under the GNU GPL. Libfuse is released under the GNU LGPLv2. All other parts (examples, fusermount, etc) are released under the GNU GPL. Under what conditions may I modify or distribute FUSE? ------------------------------------------------------ See the files COPYING and COPYING.LIB in the distribution. More information can be found at http://www.gnu.org/licenses/ Under what conditions may I distribute a filesystem which uses libfuse? ----------------------------------------------------------------------- See COPYING.LIB in the distribution. In simple terms as long as you are linking dynamically (the default) there are no limitations on linking with libfuse. For example you may distribute the filesystem itself in binary form, without source code, under any proprietary license. Under what conditions may I distribute a filesystem that uses the raw --------------------------------------------------------------------- kernel interface of FUSE? ------------------------- There are no restrictions whatsoever for using the raw kernel interface. API === Which method is called on the close() system call? -------------------------------------------------- flush() and possibly release(). For details see the documentation of these methods in Wouldn't it be simpler if there were a single close() method? ------------------------------------------------------------- No, because the relationship between the close() system call an