A Go package for implementing a FUSE file system (fork with 'almost' zero-copy read/write)
Go to file
Aaron Jacobs d800860713 Added ENOTDIR. 2015-05-26 10:47:21 +10:00
fsutil Fixed fdatasync build errors on linux. 2015-03-24 12:32:56 +11:00
fuseops Updated fuseops.Convert. 2015-05-25 14:16:19 +10:00
fusetesting Added a missing file. 2015-05-21 16:52:27 +10:00
fuseutil Added file system support. 2015-05-19 16:06:57 +10:00
samples Made "create in parallel" tests reusable. 2015-05-21 15:43:41 +10:00
.gitignore Initial commit 2015-02-27 08:52:22 +11:00
LICENSE Initial commit 2015-02-27 08:52:22 +11:00
README.md Added callouts to the samples. 2015-03-24 16:41:03 +11:00
connection.go Updated newConnection. 2015-05-25 14:17:16 +10:00
debug.go Renamed getLogger. 2015-05-25 14:19:28 +10:00
doc.go Added a callout to fuseutil.NewFileSystemServer. 2015-03-25 09:18:56 +11:00
errors.go Added ENOTDIR. 2015-05-26 10:47:21 +10:00
mounted_file_system.go Updated mounted_file_system.go. 2015-05-25 14:18:50 +10:00
unmount.go Oops, totally screwed that up. 2015-03-25 10:16:42 +11:00



This package allows for writing and mounting user-space file systems from Go. It is a wrapper around bazil.org/fuse, which does the heavy lifting. It does not make use of the bazil.org/fuse/fs sub-package, which allows for something like an object-orientend representation of files and directories, and contains a decent amount of canned behavior.

The chief improvements and/or differences from the bazil.org packages are:

  • No surprises in the form of magic/default behaviors. You must provide an implementation for every method in the interface. Embed a fuseutil.NotImplementedFileSystem struct to have default implementations that return ENOSYS.

  • Every method, struct, and field is thoroughly documented. This may help you get your bearings in the world of FUSE, the Linux VFS, traditional file system implementations, etc., all of which tend to be very poorly documented.

  • Support for arbitrary offsets in directory entries returned by ReadDir. (The bazil.org package assumes that offsets must be counts of bytes.)

The very large disadvantage over using the bazil.org packages is that many features have not yet been exposed.

Make sure to see the sub-packages of the samples package.