1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
|
General Information
===================
FUSE (Filesystem in Userspace) is a simple interface for userspace
programs to export a virtual filesystem to the linux kernel. FUSE
also aims to provide a secure method for non privileged users to
create and mount their own filesystem implementations.
You can download the source code releases from
http://sourceforge.net/projects/fuse
or alternatively you can use CVS to get the very latest development
version by setting the cvsroot to
:pserver:anonymous@cvs.sourceforge.net:/cvsroot/fuse
and checking out the 'fuse' module.
Installation
============
./configure
make
make install
modprobe fuse
Also see the file 'INSTALL'
How To Use
==========
FUSE is made up of three main parts:
- A kernel filesystem module
- A userspace library
- A mount/unmount program
Here's how to create your very own virtual filesystem in five easy
steps (after installing FUSE):
1) Edit the file example/fusexmp.c to do whatever you want...
2) Build the fusexmp program
3) run 'example/fusexmp /mnt/fuse -d'
4) ls -al /mnt/fuse
5) Be glad
If it doesn't work out, please ask! Also see the file 'include/fuse.h' for
detailed documentation of the library interface.
Security
========
If you run 'make install', the fusermount program is installed
set-user-id to root. This is done to allow normal users to mount
their own filesystem implementations.
There must however be some limitations, in order to prevent Bad User from
doing nasty things. Currently those limitations are:
- The user can only mount on a mountpoint, for which it has write
permission
- The mountpoint is not a sticky directory which isn't owned by the
user (like /tmp usually is)
- No other user (including root) can access the contents of the mounted
filesystem.
Configuration
=============
Some options regarding mount policy can be set in the file
'/etc/fuse.conf'
Currently these options are:
mount_max = NNN
Set the maximum number of FUSE mounts allowed to non-root users.
The default is 1000.
user_allow_other
Allow non-root users to specify the 'allow_other' or 'allow_root'
mount options.
Mount options
=============
These are FUSE specific mount options that can be specified for all
filesystems:
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
configuration option described in the previous section.
allow_root
This option is similar to 'allow_other' but file access is limited
to the user mounting the filesystem and root.
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.
large_read
Issue large read requests. This can improve performance for some
filesystems, but can also degrade performance. This option is only
useful on 2.4.X kernels, as on 2.6 kernels requests size is
automatically determined for optimum performance.
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).
hard_remove
The default behavior is that if an open file is deleted, the file is
renamed to a hidden file (.fuse_hiddenXXX), and only removed when
the file is finally released. This relieves the filesystem
implementation of having to deal with this problem. This option
disables the hiding behavior, and files are removed immediately in
an unlink operation (or in a rename operation which overwrites an
existing file).
debug
Turns on debug information printing by the library.
fsname=NAME
Sets the filesystem name. The default is the program name.
|