diff options
Diffstat (limited to 'ChangeLog.rst')
| -rw-r--r-- | ChangeLog.rst | 64 |
1 files changed, 52 insertions, 12 deletions
diff --git a/ChangeLog.rst b/ChangeLog.rst index a498273..0a6d00e 100644 --- a/ChangeLog.rst +++ b/ChangeLog.rst @@ -1,6 +1,35 @@ Unreleased Changes ================== +* The help text generated by fuse_lowlevel_help(), fuse_new() (and + indirectly fuse_main()) no longer includes options that are unlikely + to be of interest to end-users. The full list of accepted options is + now included in the respective function's documentation (located in + the fuse.h/fuse_lowlevel.h and doc/html). + +* The ``-o nopath`` option has been dropped - it never actually did + anything (since it is unconditionally overwritten with the value of + the `nopath` flag in `struct fuse_operations). + +* The ``-o large_read`` mount option has been dropped. Hopefully no + one uses a Linux 2.4 kernel anymore. + +* The `-o nonempty` mount point has been removed, mounting over + non-empty directories is now always allowed. This brings the + behavior of FUSE file systems in-line with the behavior of the + regular `mount` command. + + File systems that do not want to allow mounting to non-empty + directories should perform this check themselves before handing + control to libfuse. + +* The chmod, chown, truncate, utimens and getattr handlers of the + high-level API now all receive an additional struct fuse_file_info + pointer. This pointer is NULL if the file is not currently open. + + The fgetattr and ftruncate handlers have become obsolete and have + been removed. + * The `fuse_session_new` function no longer accepts the ``-o clone_fd`` option. Instead, this has become a parameter of the `fuse_session_loop_mt` and ``fuse_loop_mt` functions. @@ -9,22 +38,32 @@ Unreleased Changes the `splice_read` option is now enabled by default. As usual, this can be changed in the file system's `init` handler. -* `fuse_session_new` now treats low-level options more consistently: - First, options are used to modify FUSE defaults. Second, the file - system may inspect and/or adjust the settings in its `init` - handler. Third, command line arguments take precedence over any - modifications made by the `init` handler. +* The treatment of low-level options has been made more consistent: + + Options that can be set in the init() handler (via the + fuse_conn_info parameter) can now be set only here, + i.e. fuse_session_new() no longer accepts arguments that change the + fuse_conn_info object before or after the call do init(). As a side + effect, this removes the ambiguity where some options can be + overwritten by init(), while others overwrite the choices made by + init(). + + For file systems that wish to offer command line options for these + settings, the new fuse_parse_conn_info_opts() and + fuse_apply_conn_info_opts() functions are available. -* Removed the `async_read` field from `struct fuse_conn_info`. To - determine if the kernel supports asynchronous reads, file systems - should check the `FUSE_CAP_ASYNC_READ` bit of the `capable` - field. To enable/disable asynchronous reads, file systems should set - the flag in the `wanted` field. + Consequently, the fuse_lowlevel_help() method has been dropped. + +* The `async_read` field in `struct fuse_conn_info` has been + removed. To determine if the kernel supports asynchronous reads, + file systems should check the `FUSE_CAP_ASYNC_READ` bit of the + `capable` field. To enable/disable asynchronous reads, file systems + should set the flag in the `wanted` field. * The `fuse_parse_cmdline` function no longer prints out help when the ``--verbose`` or ``--help`` flags are given. This needs to be done - by the file system (e.g. using the `fuse_cmdline_help()`, - `fuse_lowlevel_help()` and `fuse_mount_help()` functions). + by the file system (e.g. using the `fuse_cmdline_help()` and + `fuse_lowlevel_help()` functions). * Added ``example/cuse_client.c`` to test ``example/cuse.c``. @@ -43,6 +82,7 @@ Unreleased Changes always active. File systems that want to limit the size of write requests should use the ``-o max_write=<N>`` option instead. + FUSE 3.0.0pre0 (2016-10-03) ============================ |