| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
| |
Fixes #85.
|
| |
|
|
|
|
|
| |
This should help avoid people to accidentally put options
into argv[0].
Fixes #100.
|
| |
|
|
|
|
| |
Modifying struct fuse_config in the init() handler is the canonical way
to adjust file-system implementation specific settings. There is no need
to have flags in struct fuse_operations.
|
| | |
|
| |
|
|
|
| |
Since FUSE 3 is breaking backwards compatibility, this really does
not matter.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
We now only list options that are potentially useful for an
end-user (and unlikely to accidentally break a file system). The full
list of FUSE options has been moved to the documentation of the
fuse_new() and fuse_session_new() functions.
|
| |
|
|
|
|
| |
This obsoletes the ftruncate & fgetattr handlers.
Fixes #58.
|
| |
|
|
|
|
| |
Instead of using command line options to modify struct fuse_conn_info
before and after calling the init() handler, we now give the file system
explicit control over this.
|
| |
|
|
|
|
| |
This option really affects the behavior of the session loop, not the
low-level interface. Therefore, it does not belong in the fuse_session
object.
|
| | |
|
| |
|
|
|
|
|
| |
Previously, some command line options would change the FUSE defaults
but leave the final value to the file systems `init` handler while
others would override any changes made by `init`. Now, command line
options do both: they modify the default, *and* take precedence.
|
| | |
|
| |
|
|
| |
This is redundant with the capability flags in `wants` and `capable`.
|
| |
|
|
|
|
| |
There's now a way to inhibit the "usage" line (which actually got lost
in commit 225c12aebf2d), which makes it easier for simply file-systems
to generate good-looking --help output.
|
| |
|
|
|
| |
The current behavior makes it difficult to add help for
additional options. With the change, this becomes a lot easier.
|
| |
|
|
| |
For --help and --version, it returns -1.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This option is obsolete and should always be enabled. File systems that
want to limit the size of write requests should use the
``-o max_write=<N>`` option instead.
|
| | |
|
| |
|
|
| |
Fixes #59.
|
| |
|
|
| |
Fixes #67.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Help and version messages can be generated using the new
fuse_lowlevel_help(), fuse_lowlevel_version(), fuse_mount_help(), and
fuse_mount_version() functions.
The fuse_parse_cmdline() function has been made more powerful
to do this automatically, and is now explicitly intended only
for low-level API users.
This is a code simplication patch. We don't have to parse for --help and
--version in quite as many places, and we no longer have a low-level
initialization function be responsible for the (super-high level) task
of printing a program usage message.
In the high-level API, we can now handle the command line parsing
earlier and avoid running other initialization code if we're just going
to abort later on.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The only struct fuse_chan that's available to the user application is
the one that is returned by fuse_mount. However, this is also
permanently available from struct fuse_session.
A later patch will therefore remove struct fuse_chan from the
public API completely. This patch prepares for this by changing the
fuse_lowlevel_notify_* functions to take a struct fuse_session
parameter instead of a struct fuse_chan parameter.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| | |
requirements (#29)
Remove leading _ on header guards to comply with reserved identifier requirements
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Applied (whitespace-cleanup) to each file. Having whitespace changes
in the VCS is ugly, but it ensures that in the future committers
can run this function to *avoid* commiting any whitespace.
|
| | | |
|
| |/
|
|
|
| |
Apparently f_frsize has been passed on transparently since
2b4781100812d42e704c39c51303cd28ad3f9aa6 (Nov 28, 2005).
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
Returns the full PACKAGE_VERSION string, per autoconf
|
| | |
| |
| |
| |
| | |
This creates a separate device file descriptor for each processing thread,
which might improve performance.
|
| |/
|
|
|
| |
New functions: fuse_chan_get(), fuse_chan_put(). Removed function:
fuse_chan_destroy().
|
| | |
|
| |
|
|
| |
Reported by Michael j Theall.
|
Nikolaus Rath
Sam Stuewe
Eric Engestrom
Jan Blumschein
Miklos Szeredi
Christopher Harrison
Miklos Szeredi