diff options
author | Miklos Szeredi <miklos@szeredi.hu> | 2005-07-03 18:03:11 +0000 |
---|---|---|
committer | Miklos Szeredi <miklos@szeredi.hu> | 2005-07-03 18:03:11 +0000 |
commit | bb9f51774c340883b5463aab8346dee5cef6b83d (patch) | |
tree | adc9b49c7a143285f1e78042852cfab87f54eec7 /doc/kernel.txt | |
parent | 866826d2f211298ad7a969d78d849234595d2a2e (diff) |
fix
Diffstat (limited to 'doc/kernel.txt')
-rw-r--r-- | doc/kernel.txt | 51 |
1 files changed, 51 insertions, 0 deletions
diff --git a/doc/kernel.txt b/doc/kernel.txt index afd371f..0331ccc 100644 --- a/doc/kernel.txt +++ b/doc/kernel.txt @@ -38,6 +38,57 @@ non-privileged mounts. This opens up new possibilities for the use of filesystems. A good example is sshfs: a secure network filesystem using the sftp protocol. +Mount options +~~~~~~~~~~~~~ + +'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. This option is by default only + allowed to root, but this restriction can be removed with a + (userspace) configuration option. + +'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. + +'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). + How do non-privileged mounts work? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |