path: root/Documentation
diff options
authorMiklos Szeredi <miklos@szeredi.hu>2006-12-06 20:35:44 -0800
committerLinus Torvalds <torvalds@woody.osdl.org>2006-12-07 08:39:31 -0800
commitd6392f873f1d09974d5c92c52715fa422ad7c625 (patch)
treece94449b7f2a62162fdbef0e4324c2ad8d66adbe /Documentation
parentbdcf25080438ba71bb24b885e7c102de72c25c9d (diff)
[PATCH] fuse: add support for block device based filesystems
I never intended this, but people started using fuse to implement block device based "real" filesystems (ntfs-3g, zfs). The following four patches add better support for these kinds of filesystems. Unlike "normal" fuse filesystems, using this feature should require superuser privileges (enforced by the fusermount utility). Thanks to Szabolcs Szakacsits for the input and testing. This patch adds a 'fuseblk' filesystem type, which is only different from the 'fuse' filesystem type in how the 'dev_name' mount argument is interpreted. Signed-off-by: Miklos Szeredi <miklos@szeredi.hu> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation')
1 files changed, 16 insertions, 0 deletions
diff --git a/Documentation/filesystems/fuse.txt b/Documentation/filesystems/fuse.txt
index 3d7447738958..fd17dce15a96 100644
--- a/Documentation/filesystems/fuse.txt
+++ b/Documentation/filesystems/fuse.txt
@@ -51,6 +51,22 @@ homepage:
+Filesystem type
+The filesystem type given to mount(2) can be one of the following:
+ This is the usual way to mount a FUSE filesystem. The first
+ argument of the mount system call may contain an arbitrary string,
+ which is not interpreted by the kernel.
+ The filesystem is block device based. The first argument of the
+ mount system call is interpreted as the name of the device.
Mount options