Lines Matching full:mount

33 .Nd define remote mount points for
35 mount requests
41 file specifies remote mount points for the
43 mount protocol per the
53 specifies the mount point(s) and export flags within one local server
66 In a mount entry,
75 mount points on the server.
80 is not a file system mount point, then clients will be able to access arbitrary
83 to limit exported directories to server local file system mount points.
95 mount point.
98 The first is to list all mount points as absolute
106 with respect to the client's use of the mount protocol.
111 this form allows the host(s) to mount at any point within the file system,
116 Because NFSv4 does not use the mount protocol,
148 Mount points for a file system may appear on multiple lines each with
304 export options are used to require the client to use TLS for the mount(s)
425 NFSv4 does not use the mount protocol and does permit clients to cross server
426 mount point boundaries, although not all clients are capable of crossing the
427 mount points.
463 the default remote mount-point file
471 local file system mount points, let's consider the following example:
579 .Xr mount 8
623 A client mount command for usr-ports would use the server-absolute name when
626 mount server:/wingsdl/nfsv4/usr-ports /mnt/tmp
629 A mount command using NFSv4 would use the path relative to the NFSv4
632 mount server:/usr-ports /mnt/tmp
637 The former will only ever do a v3 mount and the latter will only ever
638 do a v4 mount.
640 Note that due to different mount behavior between NFSv3 and NFSv4 a
641 NFSv4 mount request for a directory that the client does not have
643 afterwards, whereas NFSv3 rejects the mount request.
672 The export options are tied to the local mount points in the kernel and
674 server mount point.