A Go package for implementing a FUSE file system (fork with 'almost' zero-copy read/write)
Go to file
Aaron Jacobs dc5f8ae4bc Implemented GetInodeAttributes. 2015-03-17 13:46:15 +11:00
fusetesting Added linux support. 2015-03-16 12:43:35 +11:00
fuseutil Added NotImplementedFileSystem.Unlink. 2015-03-06 23:27:31 -06:00
samples Implemented GetInodeAttributes. 2015-03-17 13:46:15 +11: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 a callout to the Offset field. 2015-02-27 11:46:57 +11:00
debug.go Fixed copyright notices. 2015-03-04 08:27:42 +11:00
doc.go Fixed copyright notices. 2015-03-04 08:27:42 +11:00
errors.go Added EINVAL. 2015-03-08 17:13:43 -05:00
file_system.go Added some comments about default_permissions. 2015-03-16 13:40:04 +11:00
mounted_file_system.go Fixed copyright notices. 2015-03-04 08:27:42 +11:00
server.go Implemented convertExpirationTime. 2015-03-16 11:40:01 +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:

  • A single interface (fuse.FileSystem) for all of the methods that you might care about.

  • 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.