Lines Matching full:mount

40 .Nd mount a Fuse file system daemon
85 argument will normally be treated as the path of the special file to mount.
109 mount flag.
129 Mount on
136 Mount options are specified via
177 Besides the above mount options, there is a set of pseudo-mount options which
208 (eg, run the daemon at a low privilege level but mount it as root).
214 This is applied for Fuse mounts by default and only root can mount without
217 mount option).
224 are concerned) by doing their own secondary mount (See
228 When doing the first (primary) mount, the spawner and the mounter of the daemon
231 After the primary mount is in place, secondary mounts can be done by anyone
234 The behaviour of a secondary mount is analogous to that of symbolic
235 links: they redirect all filesystem operations to the primary mount.
237 Doing a secondary mount is like signing an agreement: by this action, the mounter
240 (either via her own mount or via the primary mount), regardless whether
244 The device name of a secondary mount is the device name of the corresponding
245 primary mount, followed by a '#' character and the index of the secondary
246 mount; e.g.,
249 System administrators might want to use a custom mount policy (ie., one going
268 (Alternatively, the daemon, the special and the mount path can be
294 will ignore unknown mount options.
314 If set, the library will not attempt to mount the filesystem, even
329 Mount the example filesystem in the Fuse distribution (from its directory):
355 .Xr mount 8 ,
376 the unmount request will be forwarded to the primary mount path.
377 In general, unmounting by device name is less error-prone than by mount path