| Commit message (Collapse) | Author | Age |
|
|
|
| |
See also issue #148.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Eventually, this setting should be negotiated in the filesystem's init()
handler (like e.g. max_write). However, this requires corresponding
changes in the FUSE kernel module. In preparation for this (and to allow
a transition period) we already allow (and require) filesystems to set
the value in the init() handler in addition to the mount option.
The end-goal is tracked in issue #91.
|
| |
|
|
|
|
| |
Also improved manpage in several ways.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Several options (use_ino, etc) depend on the file system
implementation. Allowing them to be set from the command line makes no
sense.
|
| |
|
|
|
|
|
|
| |
These are not mount options for FUSE file systems, but capabilites that
are worked out between libfuse and the fuse kernel module. For that
reason, they are also not accepted by fuse_session_new().
|
|
|
|
|
|
|
|
|
| |
* Removed -o nonempty
* Added -o noforget
* Split into high-level / low-level
* Added warning that most options should be chosen by file system
internally.
* Updated maintainer.
|
|
|
|
|
|
|
| |
big_writes has been available for some time, and is the default in FUSE
3. So max_write now actually takes effect.
(This really should have gone into commit 97f4a9cb4fc69)
|
|
|
|
| |
This was only relevant for 2.4 kernels. Fixes #92.
|
| |
|
|
Lifted from the Debian package. The man pages were written by Daniel Baumann
and Bastien Roucaries
|