A Go package for implementing a FUSE file system (fork with 'almost' zero-copy read/write)
Go to file
Aaron Jacobs 5c56db905d Updated doc.go, too. 2015-02-27 10:01:10 +11:00
fuseutil Moved NotImplementedFileSystem to reduce clutter. 2015-02-27 09:59:51 +11:00
samples Moved NotImplementedFileSystem to reduce clutter. 2015-02-27 09:59:51 +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 Moved NotImplementedFileSystem to reduce clutter. 2015-02-27 09:59:51 +11:00
debug.go Renamed package fuseutil -> fuse. 2015-02-27 08:57:18 +11:00
doc.go Updated doc.go, too. 2015-02-27 10:01:10 +11:00
errors.go Use the name bazilfuse. 2015-02-27 09:32:18 +11:00
file_system.go Moved NotImplementedFileSystem to reduce clutter. 2015-02-27 09:59:51 +11:00
mounted_file_system.go Use the name bazilfuse. 2015-02-27 09:32:18 +11:00
server.go Updated server. 2015-02-27 09:55:50 +11:00

README.md

GoDoc

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.

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