| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
| |
DragonFlyBSD has no "bsd" in uname, so add 'dragonfly' to conditionals.
-- e.g. uname(1) in DragonFlyBSD
[root@ ~]# uname
DragonFly
[root@ ~]# python -c "import sys; print(sys.platform)"
dragonfly5
|
|
|
| |
Fix spelling errors
|
|
|
|
|
| |
Were not installing the corresponding binaries either, since those
are provided by the BSD base system.
|
|
|
|
| |
Emacs now has a proper meson mode :-).
|
| |
|
| |
|
|
|
|
| |
It's just too much pain to keep it working.
|
|
|
|
| |
See also issue #148.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes: #81.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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().
|
| |
|
|
|
|
|
|
|
|
| |
Move README.NFS into doc/
Update project URL
Remove reference to non-existent INSTALL file
Remove outdated/obsolete NEWS and how-fuse-works files.
Update references to examples.
|
|
|
|
|
|
|
|
|
| |
* 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The only struct fuse_chan that's accessible to the user application is
the "master" channel that is returned by fuse_mount and stored in struct
fuse_session.
When using the multi-threaded main loop with the "clone_fd" option, each
worker thread gets its own struct fuse_chan. However, none of these are
available to the user application, nor do they hold references to struct
fuse_session (the pointer is always null).
Therefore, any presence of struct fuse_chan can be removed
without loss of functionality by relying on struct fuse_session instead.
This reduces the number of API functions and removes a potential source
of confusion (since the new API no longer looks as if it might be
possible to add multiple channels to one session, or to share one
channel between multiple sessions).
Fixes issue #17.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Distribute ulockmgr separately. It is not needed for the building of
libfuse, only fusexmp_fh. Check ulockmgr library in ./configure and if not
disable remote-lock suport in fusexmp_fh.
|
| |
|
|
|
|
|
|
| |
- modified all examples to be included in doxygen
- modified the API documentation to have more details
- added the 490px_FUSE_structure.svg.png (c) wikipedia
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Lifted from the Debian package. The man pages were written by Daniel Baumann
and Bastien Roucaries
|
|
|
|
| |
Add .gitignore files and delete .cvsignore files.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|