Lines Matching +full:can +full:- +full:secondary

61 file automatically, which can then be identified via
63 That special file can then be mounted by
105 .Bl -tag -width indent
106 .It Fl A , Ic --reject-allow_other
113 .It Fl S , Ic --safe
117 .It Fl D , Ic --daemon Ar daemon
120 .It Fl O , Ic --daemon_opts Ar opts
124 .It Fl s , Ic --special Ar special
128 .It Fl m , Ic --mountpath Ar node
131 .It Fl h , Ic --help
133 .It Fl V , Ic --version
141 .Bl -tag -width indent
145 Only root can use this option.
160 Do not refuse unmounting if there are secondary mounts.
172 This option can be used to identify the file system implemented by
177 Besides the above mount options, there is a set of pseudo-mount options which
179 One can list these by passing
184 However, there are some which do require in-kernel support.
186 .Bl -tag -width indent
214 This is applied for Fuse mounts by default and only root can mount without
224 are concerned) by doing their own secondary mount (See
227 A Fuse daemon can be shared (i.e., mounted multiple times).
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
237 Doing a secondary mount is like signing an agreement: by this action, the mounter
238 agrees that the Fuse daemon can trace her I/O activities.
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
265 non-options is allowed, but processing them stops at the third non-option
268 (Alternatively, the daemon, the special and the mount path can be
280 exception of some non-critical ones).
282 .Bl -tag -width ".Ev MOUNT_FUSEFS_SAFE"
303 .Bl -tag -width ".Ev FUSE_DEV_NAME"
318 .Bl -tag -width /dev/fuse
320 Fuse device with which the kernel and Fuse daemons can communicate.
347 (non race-free) automatic device selection:
349 .Dl #!/bin/sh -e
352 .Dl mount_fusefs -S /dev/fuse /mnt/fuse \(lq$@\(rq
365 .Pa sysutils/fusefs-kmod
374 Secondary mounts should be unmounted via their device name.
377 In general, unmounting by device name is less error-prone than by mount path