[lkml]   [2001]   [Nov]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectIntroducing FUSE: Filesystem in USErspace
Had enough of life?  Nothing to do?  Write a filesystem!

What is FUSE?

FUSE (Filesystem in USErspace) provides a simple interface for
userspace programs to export a virtual filesystem to the Linux
kernel. FUSE also aims to provide a secure method for non
privileged users to create and mount their own filesystem

There's NFS or CODA. Why FUSE?

Yes both NFS and CODA make it possible to create userspace
filesystems. But none of them were designed for this task. The
design of FUSE differs from the above in the following:

- Ability to provide a _very_ simple userspace library interface.

- Thin layer in kernel. Minimal caching, predictable behavior.

- Communication is not over a network, and is optimized for local
data transfer

- Secure environment even if userspace client is non-cooperative.

All this is nice, but does it work?

I've tested fuse with a simple 'loopback' test program, and also
with AVFS (, for which FUSE
was designed for. That doesn't mean that there are no bugs in it,
but it's a good sign...

Is it available?

Yes it can be downloaded from

How can it be installed?

FUSE currently works only on 2.4.X kernels. Installation requires
the kernel source to be present. The kernel does not need to be
patched or recompiled: the kernel part of FUSE is installed as a
module. The FUSE module is SMP safe.

There is also a kernel patch (for kernels 2.4.12 and up) included in
the distribution, which makes mounting by non-privileged users

Comments on design, implementation, and on my state of mind are

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:13    [W:0.050 / U:0.104 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site