mount.8 (c06fe0a05e6348d700e4941d30aadcdacef5d829) mount.8 (951122de0a1062504da6048883562530ec3c3c55)
1.\" Copyright (c) 1980, 1989, 1991, 1993
2.\" The Regents of the University of California. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.

--- 16 unchanged lines hidden (view full) ---

25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)mount.8 8.8 (Berkeley) 6/16/94
1.\" Copyright (c) 1980, 1989, 1991, 1993
2.\" The Regents of the University of California. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.

--- 16 unchanged lines hidden (view full) ---

25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)mount.8 8.8 (Berkeley) 6/16/94
33.\" $Id: mount.8,v 1.14 1997/02/22 14:32:43 peter Exp $
33.\" $Id: mount.8,v 1.15 1997/03/11 12:27:58 peter Exp $
34.\"
35.Dd June 16, 1994
36.Dt MOUNT 8
37.Os BSD 4
38.Sh NAME
39.Nm mount
40.Nd mount file systems
41.Sh SYNOPSIS

--- 5 unchanged lines hidden (view full) ---

47.Ar special | node
48.Nm mount
49.Op Fl dfpruvw
50.Op Fl o Ar options
51.Op Fl t Ar ufs | lfs | external_type
52.Ar special node
53.Sh DESCRIPTION
54The
34.\"
35.Dd June 16, 1994
36.Dt MOUNT 8
37.Os BSD 4
38.Sh NAME
39.Nm mount
40.Nd mount file systems
41.Sh SYNOPSIS

--- 5 unchanged lines hidden (view full) ---

47.Ar special | node
48.Nm mount
49.Op Fl dfpruvw
50.Op Fl o Ar options
51.Op Fl t Ar ufs | lfs | external_type
52.Ar special node
53.Sh DESCRIPTION
54The
55.Nm mount
55.Nm
56command
57calls the
58.Xr mount 2
59system call to prepare and graft a
60.Ar "special device"
61or the remote node (rhost:path) on to the file system tree at the point
62.Ar node .
63If either
64.Ar special
65or
66.Ar node
67are not provided, the appropriate information is taken from the
68.Xr fstab 5
69file.
70.Pp
71The system maintains a list of currently mounted file systems.
72If no arguments are given to
56command
57calls the
58.Xr mount 2
59system call to prepare and graft a
60.Ar "special device"
61or the remote node (rhost:path) on to the file system tree at the point
62.Ar node .
63If either
64.Ar special
65or
66.Ar node
67are not provided, the appropriate information is taken from the
68.Xr fstab 5
69file.
70.Pp
71The system maintains a list of currently mounted file systems.
72If no arguments are given to
73.Nm mount,
73.Nm mount ,
74this list is printed.
75.Pp
76The options are as follows:
77.Bl -tag -width indent
78.It Fl a
79All the filesystems described in
80.Xr fstab 5
81are mounted.
82Exceptions are those marked as ``noauto'' or are excluded by the
83.Fl t
84flag (see below).
85.It Fl d
86Causes everything to be done except for the actual system call.
87This option is useful in conjunction with the
88.Fl v
89flag to
90determine what the
74this list is printed.
75.Pp
76The options are as follows:
77.Bl -tag -width indent
78.It Fl a
79All the filesystems described in
80.Xr fstab 5
81are mounted.
82Exceptions are those marked as ``noauto'' or are excluded by the
83.Fl t
84flag (see below).
85.It Fl d
86Causes everything to be done except for the actual system call.
87This option is useful in conjunction with the
88.Fl v
89flag to
90determine what the
91.Nm mount
91.Nm
92command is trying to do.
93.It Fl f
94Forces the revocation of write access when trying to downgrade
95a filesystem mount status from read-write to read-only. Also
96forces the R/W mount of an unclean filesystem (dangerous; use with
97caution).
98.It Fl o
99Options are specified with a

--- 33 unchanged lines hidden (view full) ---

133.It noexec
134Do not allow execution of any binaries on the mounted file system.
135This option is useful for a server that has file systems containing
136binaries for architectures other than its own.
137.It nosuid
138Do not allow set-user-identifier or set-group-identifier bits to take effect.
139Note: this option is worthless if a public available suid or sgid
140wrapper like
92command is trying to do.
93.It Fl f
94Forces the revocation of write access when trying to downgrade
95a filesystem mount status from read-write to read-only. Also
96forces the R/W mount of an unclean filesystem (dangerous; use with
97caution).
98.It Fl o
99Options are specified with a

--- 33 unchanged lines hidden (view full) ---

133.It noexec
134Do not allow execution of any binaries on the mounted file system.
135This option is useful for a server that has file systems containing
136binaries for architectures other than its own.
137.It nosuid
138Do not allow set-user-identifier or set-group-identifier bits to take effect.
139Note: this option is worthless if a public available suid or sgid
140wrapper like
141.Xr suidperl
141.Xr suidperl 1
142is installed on your system.
143.It rdonly
144The same as
145.Fl r ;
146mount the file system read-only (even the super-user may not write it).
147.It sync
148All
149.Tn I/O

--- 14 unchanged lines hidden (view full) ---

164Any additional options specific to a filesystem type that is not
165one of the internally known types (see the
166.Fl t
167option) may be passed as a comma separated list; these options are
168distinguished by a leading
169.Dq \&-
170(dash).
171Options that take a value are specified using the syntax -option=value.
142is installed on your system.
143.It rdonly
144The same as
145.Fl r ;
146mount the file system read-only (even the super-user may not write it).
147.It sync
148All
149.Tn I/O

--- 14 unchanged lines hidden (view full) ---

164Any additional options specific to a filesystem type that is not
165one of the internally known types (see the
166.Fl t
167option) may be passed as a comma separated list; these options are
168distinguished by a leading
169.Dq \&-
170(dash).
171Options that take a value are specified using the syntax -option=value.
172For example, the mount command:
172For example, the
173.Nm
174command:
173.Bd -literal -offset indent
174mount -t mfs -o nosuid,-N,-s=4000 /dev/dk0b /tmp
175.Ed
176.Pp
177causes
175.Bd -literal -offset indent
176mount -t mfs -o nosuid,-N,-s=4000 /dev/dk0b /tmp
177.Ed
178.Pp
179causes
178.Nm mount
180.Nm
179to execute the equivalent of:
180.Bd -literal -offset indent
181/sbin/mount_mfs -o nosuid -N -s 4000 /dev/dk0b /tmp
182.Ed
183.It Fl p
184Print mount information in fstab format. Implies also the
185.Fl v
186option.

--- 19 unchanged lines hidden (view full) ---

206filesystems of the specified type.
207More than one type may be specified in a comma separated list.
208The list of filesystem types can be prefixed with
209.Dq no
210to specify the filesystem types for which action should
211.Em not
212be taken.
213For example, the
181to execute the equivalent of:
182.Bd -literal -offset indent
183/sbin/mount_mfs -o nosuid -N -s 4000 /dev/dk0b /tmp
184.Ed
185.It Fl p
186Print mount information in fstab format. Implies also the
187.Fl v
188option.

--- 19 unchanged lines hidden (view full) ---

208filesystems of the specified type.
209More than one type may be specified in a comma separated list.
210The list of filesystem types can be prefixed with
211.Dq no
212to specify the filesystem types for which action should
213.Em not
214be taken.
215For example, the
214.Nm mount
216.Nm
215command:
216.Bd -literal -offset indent
217mount -a -t nonfs,mfs
218.Ed
219.Pp
220mounts all filesystems except those of type
221.Tn NFS
222and
223.Tn MFS .
224.Pp
225If the type is not one of the internally known types,
217command:
218.Bd -literal -offset indent
219mount -a -t nonfs,mfs
220.Ed
221.Pp
222mounts all filesystems except those of type
223.Tn NFS
224and
225.Tn MFS .
226.Pp
227If the type is not one of the internally known types,
226mount will attempt to execute a program in
228.Nm
229will attempt to execute a program in
227.Pa /sbin/mount_ Ns Em XXX
228where
229.Em XXX
230is replaced by the type name.
231For example, nfs filesystems are mounted by the program
232.Pa /sbin/mount_nfs .
233.Pp
234Most filesystems will be dynamically loaded by their mount programs

--- 21 unchanged lines hidden (view full) ---

256also a file system can be changed from read-only to read-write
257or vice versa.
258An attempt to change from read-write to read-only will fail if any
259files on the filesystem are currently open for writing unless the
260.Fl f
261flag is also specified.
262The set of options is determined by first extracting the options
263for the file system from the
230.Pa /sbin/mount_ Ns Em XXX
231where
232.Em XXX
233is replaced by the type name.
234For example, nfs filesystems are mounted by the program
235.Pa /sbin/mount_nfs .
236.Pp
237Most filesystems will be dynamically loaded by their mount programs

--- 21 unchanged lines hidden (view full) ---

259also a file system can be changed from read-only to read-write
260or vice versa.
261An attempt to change from read-write to read-only will fail if any
262files on the filesystem are currently open for writing unless the
263.Fl f
264flag is also specified.
265The set of options is determined by first extracting the options
266for the file system from the
264.Xr fstab
267.Xr fstab 5
265table,
266then applying any options specified by the
267.Fl o
268argument,
269and finally applying the
270.Fl r
271or
272.Fl w

--- 27 unchanged lines hidden (view full) ---

300.Xr mount_procfs 8 ,
301.Xr mount_umap 8 ,
302.Xr mount_union 8 ,
303.Xr umount 8
304.Sh BUGS
305It is possible for a corrupted file system to cause a crash.
306.Sh HISTORY
307A
268table,
269then applying any options specified by the
270.Fl o
271argument,
272and finally applying the
273.Fl r
274or
275.Fl w

--- 27 unchanged lines hidden (view full) ---

303.Xr mount_procfs 8 ,
304.Xr mount_umap 8 ,
305.Xr mount_union 8 ,
306.Xr umount 8
307.Sh BUGS
308It is possible for a corrupted file system to cause a crash.
309.Sh HISTORY
310A
308.Nm mount
311.Nm
309command appeared in
310.At v1 .
312command appeared in
313.At v1 .