Fuse github

Fuse github DEFAULT
General Information =================== FUSE (Filesystem in Userspace) is 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 implementations. You can download the source code releases from http://sourceforge.net/projects/fuse or alternatively you can use CVS to get the very latest development version: cvs -d :pserver:[email protected]:/cvsroot/fuse co fuse Dependencies ============ Linux kernel version 2.6.X where X >= 9. Alternatively a kernel module from FUSE release 2.5.* can be used with this release, which supports kernels >= 2.4.21. Installation ============ ./configure make make install modprobe fuse You may also need to add '/usr/local/lib' to '/etc/ld.so.conf' and/or run ldconfig. You'll also need a fuse kernel module, Linux kernels 2.6.14 or later contain FUSE support. For more details see the file 'INSTALL' How To Use ========== FUSE is made up of three main parts: - A kernel filesystem module - A userspace library - A mount/unmount program Here's how to create your very own virtual filesystem in five easy steps (after installing FUSE): 1) Edit the file example/fusexmp.c to do whatever you want... 2) Build the fusexmp program 3) run 'example/fusexmp /mnt/fuse -d' 4) ls -al /mnt/fuse 5) Be glad If it doesn't work out, please ask! Also see the file 'include/fuse.h' for detailed documentation of the library interface. Security ======== If you run 'make install', the fusermount program is installed set-user-id to root. This is done to allow normal users to mount their own filesystem implementations. There must however be some limitations, in order to prevent Bad User from doing nasty things. Currently those limitations are: - The user can only mount on a mountpoint, for which it has write permission - The mountpoint is not a sticky directory which isn't owned by the user (like /tmp usually is) - No other user (including root) can access the contents of the mounted filesystem. Configuration ============= Some options regarding mount policy can be set in the file '/etc/fuse.conf' Currently these options are: mount_max = NNN Set the maximum number of FUSE mounts allowed to non-root users. The default is 1000. user_allow_other Allow non-root users to specify the 'allow_other' or 'allow_root' mount options. Mount options ============= Most of the generic mount options described in 'man mount' are supported (ro, rw, suid, nosuid, dev, nodev, exec, noexec, atime, noatime, sync async, dirsync). Filesystems are mounted with '-onodev,nosuid' by default, which can only be overridden by a privileged user. These are FUSE specific mount options that can be specified for all filesystems: default_permissions By default FUSE doesn't check file access permissions, the filesystem is free to implement it's access policy or leave it to the underlying file access mechanism (e.g. in case of network filesystems). This option enables permission checking, restricting access based on file mode. This is option is usually useful together with the 'allow_other' mount option. allow_other This option overrides the security measure restricting file access to the user mounting the filesystem. So all users (including root) can access the files. This option is by default only allowed to root, but this restriction can be removed with a configuration option described in the previous section. allow_root This option is similar to 'allow_other' but file access is limited to the user mounting the filesystem and root. This option and 'allow_other' are mutually exclusive. kernel_cache This option disables flushing the cache of the file contents on every open(). This should only be enabled on filesystems, where the file data is never changed externally (not through the mounted FUSE filesystem). Thus it is not suitable for network filesystems and other "intermediate" filesystems. NOTE: if this option is not specified (and neither 'direct_io') data is still cached after the open(), so a read() system call will not always initiate a read operation. auto_cache This option enables automatic flushing of the data cache on open(). The cache will only be flushed if the modification time or the size of the file has changed. large_read Issue large read requests. This can improve performance for some filesystems, but can also degrade performance. This option is only useful on 2.4.X kernels, as on 2.6 kernels requests size is automatically determined for optimum performance. direct_io This option disables the use of page cache (file content cache) in the kernel for this filesystem. This has several affects: - Each read() or write() system call will initiate one or more read or write operations, data will not be cached in the kernel. - The return value of the read() and write() system calls will correspond to the return values of the read and write operations. This is useful for example if the file size is not known in advance (before reading it). max_read=N With this option the maximum size of read operations can be set. The default is infinite. Note that the size of read requests is limited anyway to 32 pages (which is 128kbyte on i386). max_readahead=N Set the maximum number of bytes to read-ahead. The default is determined by the kernel. On linux-2.6.22 or earlier it's 131072 (128kbytes) max_write=N Set the maximum number of bytes in a single write operation. The default is 128kbytes. Note, that due to various limitations, the size of write requests can be much smaller (4kbytes). This limitation will be removed in the future. async_read Perform reads asynchronously. This is the default sync_read Perform all reads (even read-ahead) synchronously. hard_remove The default behavior is that if an open file is deleted, the file is renamed to a hidden file (.fuse_hiddenXXX), and only removed when the file is finally released. This relieves the filesystem implementation of having to deal with this problem. This option disables the hiding behavior, and files are removed immediately in an unlink operation (or in a rename operation which overwrites an existing file). It is recommended that you not use the hard_remove option. When hard_remove is set, the following libc functions fail on unlinked files (returning errno of ENOENT): - read() - write() - fsync() - close() - f*xattr() - ftruncate() - fstat() - fchmod() - fchown() debug Turns on debug information printing by the library. fsname=NAME Sets the filesystem source (first field in /etc/mtab). The default is the program name. subtype=TYPE Sets the filesystem type (third field in /etc/mtab). The default is the program name. If the kernel suppports it, /etc/mtab and /proc/mounts will show the filesystem type as "fuse.TYPE" If the kernel doesn't support subtypes, the source filed will be "TYPE#NAME", or if fsname option is not specified, just "TYPE". use_ino Honor the 'st_ino' field in getattr() and fill_dir(). This value is used to fill in the 'st_ino' field in the stat()/lstat()/fstat() functions and the 'd_ino' field in the readdir() function. The filesystem does not have to guarantee uniqueness, however some applications rely on this value being unique for the whole filesystem. readdir_ino If 'use_ino' option is not given, still try to fill in the 'd_ino' field in readdir(). If the name was previously looked up, and is still in the cache, the inode number found there will be used. Otherwise it will be set to '-1'. If 'use_ino' option is given, this option is ignored. nonempty Allows mounts over a non-empty file or directory. By default these mounts are rejected (from version 2.3.1) to prevent accidental covering up of data, which could for example prevent automatic backup. umask=M Override the permission bits in 'st_mode' set by the filesystem. The resulting permission bits are the ones missing from the given umask value. The value is given in octal representation. uid=N Override the 'st_uid' field set by the filesystem. gid=N Override the 'st_gid' field set by the filesystem. blkdev Mount a filesystem backed by a block device. This is a privileged option. The device must be specified with the 'fsname=NAME' option. entry_timeout=T The timeout in seconds for which name lookups will be cached. The default is 1.0 second. For all the timeout options, it is possible to give fractions of a second as well (e.g. "-oentry_timeout=2.8") negative_timeout=T The timeout in seconds for which a negative lookup will be cached. This means, that if file did not exist (lookup retuned ENOENT), the lookup will only be redone after the timeout, and the file/directory will be assumed to not exist until then. The default is 0.0 second, meaning that caching negative lookups are disabled. attr_timeout=T The timeout in seconds for which file/directory attributes are cached. The default is 1.0 second. ac_attr_timeout=T The timeout in seconds for which file attributes are cached for the purpose of checking if "auto_cache" should flush the file data on open. The default is the value of 'attr_timeout' intr Allow requests to be interrupted. Turning on this option may result in unexpected behavior, if the filesystem does not support request interruption. intr_signal=NUM Specify which signal number to send to the filesystem when a request is interrupted. The default is 10 (USR1). modules=M1[:M2...] Add modules to the filesystem stack. Modules are pushed in the order they are specified, with the original filesystem being on the bottom of the stack. Modules distributed with fuse ----------------------------- iconv ````` Perform file name character set conversion. Options are: from_code=CHARSET Character set to convert from (see iconv -l for a list of possible values). Default is UTF-8. to_code=CHARSET Character set to convert to. Default is determined by the current locale. subdir `````` Prepend a given directory to each path. Options are: subdir=DIR Directory to prepend to all paths. This option is mandatory. rellinks Transform absolute symlinks into relative norellinks Do not transform absolute symlinks into relative. This is the default. Reporting bugs ============== Please send bug reports to the <[email protected]> mailing list. The list is open, you need not be subscribed to post.
Sours: https://github.com/fuse4x/fuse

Awesome FUSE Filesystem

This is a list of resources related to [FUSE] (https://en.wikipedia.org/wiki/Filesystem_in_Userspace), Filesystem in Userspace. (This is different from https://github.com/vinkla/awesome-fuse). This is a Golang heavy list, please help me add other languages to it by opening a PR today!

Table of Contents

Libraries

  • osxfuse - For OSX. Language: C.
  • libfuse - Reference implementation for Linux FUSE. Language: C.
  • Dokan - For Windows; has a FUSE wrapper.
  • jacobsa/fuse - A Go package for implementing a FUSE file system. Language: Golang.
  • bazil/fuse - FUSE library for Go. Language: Golang.
  • go-fuse - FUSE bindings for Go. Language: Golang.
  • ruse-fuse - Rust library for filesystems in userspace (FUSE). Language: Rust.
  • rfusefs - Ruby FUSE filesystem - write filesystems in Ruby (FuseFS API over rfuse). Language: Ruby.
  • fuse4js - FUSE bindings for Javascript and node.js (possibly outdated). Language: Javascript.
  • fuse-google-drive - A fuse http://loggedfs.sourceforge.net filesystem wrapper for Google Drive.

Built On

  • gcsfuse - A user-space file system for interacting with Google Cloud Storage. Language: Golang.
  • sshfs - File system based on the SSH File Transfer Protocol; same authors as osxfuse. Language: C.
  • sshfs - A network filesystem client to connect to SSH servers; same authors as libfuse. Language: C.
  • go-ipfs - IPFS implementation in go. Language: Golang.
  • mirrorfs - Go filesystem project using bazil/fuse. Language: Golang.
  • gocryptfs - Encrypted overlay filesystem written in Go. Language: Golang.
  • tahoe-lafs - The Tahoe-LAFS decentralized secure filesystem. Language: Python.
  • btfs - A bittorrent filesystem based on FUSE. Language: C++.
  • google-drive-ocamlfuse - FUSE filesystem over Google Drive. Language: OCaml.
  • mp3fs - FUSE-based transcoding filesystem from FLAC to MP3. Language: C++.
  • encfs - An Encrypted Filesystem for FUSE. Language: C++.
  • GDriveFS - An innovative FUSE wrapper for Google Drive; Language: Python.
  • pachyderm - Containerized Data Analytics. Language: Golang.
  • camlistore - Personal storage system for life: a way of storing, syncing, sharing, modelling and backing up content. Language: Golang.
  • svfs - The Swift Virtual File System. Language: Golang.
  • restic - restic backup program. Language: Golang.
  • unionfs-fuse - union filesystem using fuse. Language: C.
  • GlusterFS - Storage for your Cloud. Language: C.
  • LoggedFS - Filesystem monitoring with Fuse. Language: C++.
  • go-mtpfs - Mount MTP devices over FUSE. Language: Go.
  • πfs - Filesystem that stores your data in π. Language: C.
  • s3fs - FUSE-based file system backed by Amazon S3. Language: C++.

Posts

Misc

License

CC0

Sours: https://github.com/koding/awesome-fuse-fs
  1. Bmw e46 vanos
  2. Ddr dreamcast
  3. Sam storage asset management
  4. Sqlcode = 0

libfuse

About

FUSE (Filesystem in Userspace) is an interface for userspace programs to export a filesystem to the Linux kernel. The FUSE project consists of two components: the fuse kernel module (maintained in the regular kernel repositories) and the libfuse userspace library (maintained in this repository). libfuse provides the reference implementation for communicating with the FUSE kernel module.

A FUSE file system is typically implemented as a standalone application that links with libfuse. libfuse provides functions to mount the file system, unmount it, read requests from the kernel, and send responses back. libfuse offers two APIs: a "high-level", synchronous API, and a "low-level" asynchronous API. In both cases, incoming requests from the kernel are passed to the main program using callbacks. When using the high-level API, the callbacks may work with file names and paths instead of inodes, and processing of a request finishes when the callback function returns. When using the low-level API, the callbacks must work with inodes and responses must be sent explicitly using a separate set of API functions.

Development Status

libfuse is shipped by all major Linux distributions and has been in production use across a wide range of systems for many years. However, at present libfuse does not have any active, regular contributors. The current maintainer continues to apply pull requests and makes regular releases, but unfortunately has no capacity to do any development beyond addressing high-impact issues. When reporting bugs, please understand that unless you are including a pull request or are reporting a critical issue, you will probably not get a response. If you are using libfuse, please consider contributing to the project.

Supported Platforms

  • Linux (fully)
  • BSD (mostly/best-effort)
  • For OS-X, please use OSXFUSE

Installation

You can download libfuse from https://github.com/libfuse/libfuse/releases. To build and install, you must use Meson and Ninja. After extracting the libfuse tarball, create a (temporary) build directory and run Meson:

Normally, the default build options will work fine. If you nevertheless want to adjust them, you can do so with the meson configure command:

To build, test, and install libfuse, you then use Ninja:

Running the tests requires the py.test Python module. Instead of running the tests as root, the majority of tests can also be run as a regular user if util/fusermount3 is made setuid root first:

Security implications

The fusermount3 program is installed setuid root. This is done to allow normal users to mount their own filesystem implementations.

To limit the harm that malicious users can do this way, fusermount3 enforces the following limitations:

  • The user can only mount on a mountpoint for which they have write permission

  • The mountpoint must not be a sticky directory which isn't owned by the user (like /tmp usually is)

  • No other user (including root) can access the contents of the mounted filesystem (though this can be relaxed by allowing the use of the allow_other and allow_root mount options in /etc/fuse.conf)

If you intend to use the allow_other mount options, be aware that FUSE has an unresolved security bug: if the default_permissions mount option is not used, the results of the first permission check performed by the file system for a directory entry will be re-used for subsequent accesses as long as the inode of the accessed entry is present in the kernel cache - even if the permissions have since changed, and even if the subsequent access is made by a different user. This is of little concern if the filesystem is accessible only to the mounting user (which has full access to the filesystem anyway), but becomes a security issue when other users are allowed to access the filesystem (since they can exploit this to perform operations on the filesystem that they do not actually have permissions for).

This bug needs to be fixed in the Linux kernel and has been known since 2006 but unfortunately no fix has been applied yet. If you depend on correct permission handling for FUSE file systems, the only workaround is to use (which does not currently support ACLs), or to completely disable caching of directory entry attributes.

Building your own filesystem

FUSE comes with several example file systems in the directory. For example, the passthrough examples mirror the contents of the root directory under the mountpoint. Start from there and adapt the code!

The documentation of the API functions and necessary callbacks is mostly contained in the files (for the high-level API) and (for the low-level API). An autogenerated html version of the API is available in the directory and at http://libfuse.github.io/doxygen.

Getting Help

If you need help, please ask on the [email protected] mailing list (subscribe at https://lists.sourceforge.net/lists/listinfo/fuse-devel).

Please report any bugs on the GitHub issue tracker at https://github.com/libfuse/libfuse/issues.

Sours: https://github.com/libfuse/libfuse
Fuse x Pocket Network AMA with the Founders (19.08.21)

Fuse.js

Node.js CIVersionDownloadscode style: prettierContributorsLicense

Supporting Fuse.js

Through contributions, donations, and sponsorship, you allow Fuse.js to thrive. Also, you will be recognized as a beacon of support to open-source developers.


Introduction

Fuse.js is a lightweight fuzzy-search, in JavaScript, with zero dependencies.

Browser Compatibility

Fuse.js supports all browsers that are ES5-compliant (IE8 and below are not supported).

Documentation

To check out a live demo and docs, visit fusejs.io.

Develop

Here's a separate document for developers.

Contribute

We've set up a separate document for our contribution guidelines.

Sours: https://github.com/krisk/Fuse

Github fuse

Extension Framework for FUSE

We have modifed the FUSE driver to support ExtFUSE feature. Therefore, you will have to install and run a our modified kernel. To clone the kernel sources do:

In menuconfig step, DO NOT select FUSE as a kernel module as it will cause the kernel compilation to fail; instead, build FUSE into the kernel.

Boot into the new kernel. Clone ExtFUSE library sources and build. Export the path to repo as EXTFUSE_REPO_PATH. You will need LLVM/Clang toolchain to build.

The eBPF code for handling FUSE requests in the kernel can be found in . Once you build the library, compiled eBPF bytecode can be found in .

Finally, you will also need a modified FUSE library. To clone its source repo:

Follow instructions here to build libfuse. NOTE that you will need to run to create the script.

You can test ExtFUSE functionality with a simple stackable FUSE file system here. NOTE that you will need to copy to before you test StackFS because the name and path is hard-coded in .

Sours: https://github.com/extfuse/extfuse
Awesome GitHub Profile Design with Profile README (RU)

s3fs

s3fs allows Linux, macOS, and FreeBSD to mount an S3 bucket via FUSE. s3fs preserves the native object format for files, allowing use of other tools like AWS CLI.
s3fs-fuse CITwitter Follow

Features

  • large subset of POSIX including reading/writing files, directories, symlinks, mode, uid/gid, and extended attributes
  • compatible with Amazon S3, and other S3-based object stores
  • allows random writes and appends
  • large files via multi-part upload
  • renames via server-side copy
  • optional server-side encryption
  • data integrity via MD5 hashes
  • in-memory metadata caching
  • local disk data caching
  • user-specified regions, including Amazon GovCloud
  • authenticate via v2 or v4 signatures

Installation

Many systems provide pre-built packages:

  • Amazon Linux via EPEL:

  • Arch Linux:

  • Debian 9 and Ubuntu 16.04 or newer:

  • Fedora 27 or newer:

  • Gentoo:

  • RHEL and CentOS 7 or newer via EPEL:

  • SUSE 12 and openSUSE 42.1 or newer:

  • macOS via Homebrew:

  • FreeBSD:

Note: Homebrew has deprecated osxfuse and s3fs may not install any more, see #1618.

Otherwise consult the compilation instructions.

Examples

s3fs supports the standard AWS credentials file stored in . Alternatively, s3fs supports a custom passwd file.

The default location for the s3fs password file can be created:

  • using a file in the users home directory (i.e. )
  • using the system-wide file

Enter your credentials in a file and set owner-only permissions:

Run s3fs with an existing bucket and directory :

If you encounter any errors, enable debug output:

You can also mount on boot by entering the following line to :

If you use s3fs with a non-Amazon S3 implementation, specify the URL and path-style requests:

or(fstab)

Note: You may also want to create the global credential file first

Note2: You may also need to make sure service is start on boot

Limitations

Generally S3 cannot offer the same performance or semantics as a local file system. More specifically:

  • random writes or appends to files require rewriting the entire object, optimized with multi-part upload copy
  • metadata operations such as listing directories have poor performance due to network latency
  • non-AWS providers may have eventual consistency so reads can temporarily yield stale data (AWS offers read-after-write consistency since Dec 2020)
  • no atomic renames of files or directories
  • no coordination between multiple clients mounting the same bucket
  • no hard links
  • inotify detects only local modifications, not external ones by other clients or tools

References

  • goofys - similar to s3fs but has better performance and less POSIX compatibility
  • s3backer - mount an S3 bucket as a single file
  • S3Proxy - combine with s3fs to mount Backblaze B2, EMC Atmos, Microsoft Azure, and OpenStack Swift buckets
  • s3ql - similar to s3fs but uses its own object format
  • YAS3FS - similar to s3fs but uses SNS to allow multiple clients to mount a bucket

Frequently Asked Questions

License

Copyright (C) 2010 Randy Rizun [email protected]

Licensed under the GNU GPL version 2

Sours: https://github.com/s3fs-fuse/s3fs-fuse

Now discussing:

@osxfuse

Pinned

  1. osxfusePublic

    FUSE extends macOS by adding support for user space file systems

    7.1k 456

  2. sshfsPublic

    File system based on the SSH File Transfer Protocol

    C 911 100

Repositories

  • fuse Public

    C-based FUSE for macOS SDK

    C 145 70 0 6 Updated

  • sshfs Public

    File system based on the SSH File Transfer Protocol

    C 911 GPL-2.0 100 36 2 Updated

  • kext Public

    FUSE kernel extension

    C 72 46 0 2 Updated

  • framework Public

    Objective-C-based FUSE for macOS SDK

    Objective-C 54 41 0 2 Updated

  • support Public

    FUSE for macOS support tools

    Shell 20 25 1 0 Updated

  • prefpane Public

    FUSE for macOS preference pane

    Objective-C 43 32 0 0 Updated

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.

Sours: https://github.com/osxfuse


323 324 325 326 327