e0296dec95
There's no reason for this to be enforced on the user. For use-cases such as S3-backing, there are no "permissions" of such to base this on. Consequently, everything ends up being owned as root and making it far more difficult to use. It should, however, be optional. |
||
---|---|---|
fsutil | ||
fuseops | ||
fusetesting | ||
fuseutil | ||
internal | ||
samples | ||
.gitignore | ||
.travis.yml | ||
LICENSE | ||
README.md | ||
connection.go | ||
conversions.go | ||
debug.go | ||
doc.go | ||
errors.go | ||
freelists.go | ||
mount.go | ||
mount_config.go | ||
mount_darwin.go | ||
mount_linux.go | ||
mount_test.go | ||
mounted_file_system.go | ||
ops.go | ||
unmount.go | ||
unmount_linux.go | ||
unmount_std.go |
README.md
This package allows for writing and mounting user-space file systems from Go. Install it as follows:
go get -u github.com/jacobsa/fuse
Afterward, see the documentation for the following three packages:
-
Package fuse provides support for mounting a new file system and reading requests from the kernel.
-
Package fuseops enumerates the supported requests from the kernel, and provides documentation on their semantics.
-
Package fuseutil, in particular the
FileSystem
interface, provides a convenient way to create a file system type and export it to the kernel viafuse.Mount
.
Make sure to also see the sub-packages of the samples package for examples and tests.
This package owes its inspiration and most of its kernel-related code to bazil.org/fuse.