|
|
1.1 root 1: .\" Copyright (c) 1980, 1989 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted provided
5: .\" that: (1) source distributions retain this entire copyright notice and
6: .\" comment, and (2) distributions including binaries display the following
7: .\" acknowledgement: ``This product includes software developed by the
8: .\" University of California, Berkeley and its contributors'' in the
9: .\" documentation or other materials provided with the distribution and in
10: .\" all advertising materials mentioning features or use of this software.
11: .\" Neither the name of the University nor the names of its contributors may
12: .\" be used to endorse or promote products derived from this software without
13: .\" specific prior written permission.
14: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
15: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
16: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
17: .\"
18: .\" @(#)mount.8 6.15 (Berkeley) 6/24/90
19: .\"
20: .TH MOUNT 8 "June 24, 1990"
21: .UC 4
22: .SH NAME
23: mount, umount \- mount and dismount file systems
24: .SH SYNOPSIS
25: .B mount
26: [
27: .B \-afrwu
28: ] [
29: .B \-t
30: nfs | ufs | external_type
31: ]
32: .br
33: .B mount
34: [
35: .B \-frwu
36: ]
37: special | node
38: .br
39: .B mount
40: [
41: .B \-frwu
42: ] [
43: .B \-t
44: nfs | ufs | external_type
45: ] [
46: .B \-o
47: options
48: ]
49: special node
50: .br
51: .PP
52: .B umount
53: [
54: .B \-af
55: ] [
56: .B \-t
57: nfs | ufs | external_type
58: ]
59: .br
60: .B umount
61: [
62: .B \-f
63: ]
64: special | node
65: .br
66: .SH DESCRIPTION
67: .I Mount
68: announces to the system that a removable file system is present on the
69: block device \fIspecial\fP or the remote node ``rhost:path''.
70: The file \fInode\fP must exist already and
71: it must be a directory. It becomes the name of the newly mounted root.
72: The optional arguments \fI-r\fP and \fI-w\fP indicate that the file
73: system is to be mounted read-only or read-write, respectively.
74: If either \fIspecial\fP or \fIfile\fP are not provided, the appropriate
75: information is taken from the \fIfstab\fP file. The \fI-f\fP option
76: causes everything to be done except for the actual system call; if it's
77: not obvious, this ``fakes'' mounting the file system.
78: This option is useful in conjunction with the \fI-v\fP flag to
79: determine what the
80: .I mount
81: command is trying to do.
82: .PP
83: The optional argument \fI-t\fP can be used
84: to indicate the file system type.
85: The type \fBufs\fP is the default.
86: If the type is not one of the internally known types,
87: mount will attempt to execute a program in
88: .B /sbin/mount_XXX
89: where \fBXXX\fP is replaced by the type name.
90: The standard mount options (see below) are parsed and
91: passed to external program via the \fI-F\fP option
92: as a decimal number.
93: Any additional options specific to the program can
94: be passed as a comma separated list;
95: these options are distinguished by starting with a \fI-\fP (dash).
96: Those options that take a value are specified
97: using the syntax -option=value.
98: For example, the mount command:
99: .br
100: mount -t mfs -o nosuid,-N,-s=4000 /dev/dk0b /tmp
101: .br
102: causes mount to attempt to execute:
103: .br
104: /sbin/mount_mfs -F 8 -N -s 4000 /dev/dk0b /tmp
105: .PP
106: Options are specified by a \fI-o\fP argument
107: followed by a comma separated string of options.
108: The following options apply to any file system that is being mounted:
109: .IP "noexec" 12
110: Do not allow execution of any binaries on the mounted file system.
111: This options is useful for a server that has file systems containing
112: binaries for architectures other than its own.
113: .IP "nosuid" 12
114: Do not allow set-user-identifier or set-group-identifier bits to take effect.
115: .IP "nodev" 12
116: Do not interpret character or block special devices on the file system.
117: This options is useful for a server that has file systems containing
118: special devices for architectures other than its own.
119: .IP "synchronous" 12
120: All I/O to the file system should be done synchronously.
121: .PP
122: The \fI-u\fP flag indicates that the status of an already mounted file
123: system should be changed.
124: Any of the options above may be changed;
125: also a file system can be changed from read-only to read-write.
126: The set of options is determined by first extracting the options
127: for the file system from the \fIfstab\fP table,
128: then applying any options specified by the \fI-o\fP argument,
129: and finally applying the \fI-r\fP or \fI-w\fP option.
130: .PP
131: The following list can be used to override
132: the defaults for an nfs mount:
133: .IP "hard" 12
134: I/O system calls will retry until the server responds (default)
135: .IP "soft" 12
136: I/O system calls will fail and return errno after \fIretrans\fP request
137: retransmissions
138: .IP "spongy" 12
139: Soft semantics for the stat, lookup, fsstat, readlink and readdir
140: filesystem operations and hard semantics for the others.
141: This option is meant to be similar to hard,
142: except that processes will not be hung forever when
143: they trip over mount points to dead servers.
144: .IP "bg" 12
145: If the first mount request times out, do retries in background
146: .IP "intr" 12
147: I/O system calls can be interrupted.
148: .IP "noconn" 12
149: Do not connect the socket.
150: Used for UDP servers that send replies from a
151: socket other than the nfs server socket.
152: .IP "tcp" 12
153: Use TCP transport instead of UDP.
154: .IP "rsize=#" 12
155: Set read size to \fI#\fP bytes.
156: .IP "wsize=#" 12
157: Set write size to \fI#\fP bytes.
158: .IP "retry=#" 12
159: Set mount retry count to \fI#\fP.
160: .IP "retrans=#" 12
161: Set retransmission count for nfs rpc's to \fI#\fP.
162: .IP "timeo=#" 12
163: Set initial nfs timeout to \fI#\fP in 0.1 sec intervals.
164: .fi
165: .PP
166: .I Umount
167: announces to the system that the removable file system \fInode\fP
168: or whatever removable file system was previously mounted on device
169: \fIspecial\fP should be removed.
170: If the \fI-f\fP option is specified for
171: .IR umount ,
172: the file system is forcibly unmounted.
173: Active special devices continue to work,
174: but all other files return errors if further accesses are attempted.
175: The root file system cannot be forcibly unmounted.
176: .PP
177: If the \fI-a\fP option is present for either
178: .I mount
179: or
180: .I umount,
181: all of the file systems described in
182: .I fstab
183: are mounted or unmounted.
184: The optional argument \fI-t\fP can be used
185: to indicate that the actions should only be taken on
186: filesystems of the specified type.
187: More than one type may be specified in a comma separated list.
188: The list of filesystem types can be prefixed with ``no'' to
189: specify the filesystem types on which no action should be taken.
190: For example, the mount command:
191: .br
192: mount -a -t nonfs,mfs
193: .br
194: mounts all filesystems except those of type NFS and MFS.
195: .PP
196: The system maintains a list of currently mounted file systems.
197: If invoked without an argument,
198: .I mount
199: prints the list.
200: The optional argument \fI-t\fP can be used
201: to indicate that only filesystems of the specified type
202: should be listed.
203: More than one type may be specified in a comma separated list.
204: The list of filesystem types can be prefixed with ``no'' to
205: indicate the types of filesystems to be excluded from the listing.
206: .PP
207: Physically write-protected and magnetic tape file
208: systems must be mounted read-only
209: or errors will occur when access times are updated,
210: whether or not any explicit write is attempted.
211: .SH FILES
212: /etc/fstab file system table
213: .SH "SEE ALSO"
214: mount(2), unmount(2), fstab(5)
215: .SH BUGS
216: Mounting garbaged file systems will crash the system.
217: .PP
218: Mounting a root directory on a non-directory
219: makes some apparently good path names invalid.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.