2 .\" Copyright (c) 2008 Sun Microsystems, Inc. All Rights Reserved.
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH MOUNT_UDFS 1M "May 12, 2008"
8 mount_udfs \- mount a udfs file system
12 \fBmount\fR \fB-F\fR udfs [\fIgeneric_options\fR] [\fB-o\fR \fIspecific_options\fR]
13 [\fB-O\fR] \fIspecial\fR \fImount_point\fR
18 \fBmount\fR \fB-F\fR udfs [\fIgeneric_options\fR] [\fB-o\fR \fIspecific_options\fR]
19 [\fB-O\fR] \fIspecial\fR | \fImount_point\fR
25 The \fBmount\fR utility attaches a \fBudfs\fR file system to the file system
26 hierarchy at the \fImount_point\fR, which is the pathname of a directory. If
27 \fImount_point\fR has any contents prior to the mount operation, these are
28 hidden until the file system is unmounted.
31 If mount is invoked with either \fIspecial\fR or \fImount_point\fR as the only
32 arguments, \fBmount\fR searches \fB/etc/vfstab\fR to fill in the missing
33 arguments, including the \fIspecific_options\fR. See \fBmount\fR(1M).
36 The \fBudfs\fR file system supports direct mounting of files containing the
37 file system as well as block devices. See \fBmount\fR(1M) and
41 If \fIspecial\fR and \fImount_point\fR are specified without any
42 \fIspecific_options\fR, the default is \fBrw\fR.
45 If the directory on which a file system is to be mounted is a symbolic link,
46 the file system is mounted on the directory to which the symbolic link refers,
47 rather than on top of the symbolic link itself.
51 See \fBmount\fR(1M) for the list of supported \fIgeneric_options\fR.
54 The following options are supported:
58 \fB\fB-o\fR \fIspecific_options\fR\fR
62 Specify \fBudfs\fR file system specific options in a comma-separated list with
63 no intervening spaces. The following \fIspecific_options\fR are available:
71 Mount the file system without making an entry in \fB/etc/mnttab\fR.
81 Remount the file system as read-write. The option is used in conjunction with
84 A file system mounted read-only can be remounted as read-write. This option
85 fails if the file system is not currently mounted.
97 Overlay mount. Allow the file system to be mounted over an existing mount
98 point, making the underlying file system inaccessible. If a mount is attempted
99 on a pre-existing mount point without setting this flag, the mount fails,
100 producing the error: \f(CWdevice busy\fR.
107 \fB\fB/etc/mnttab\fR\fR
111 Table of mounted file systems
117 \fB\fB/etc/vfstab\fR\fR
121 List of default parameters for each file system
127 \fBfsck\fR(1M), \fBfsck_udfs\fR(1M), \fBlofiadm\fR(1M), \fBmount\fR(1M),
128 \fBmountall\fR(1M), \fBmount\fR(2), \fBmnttab\fR(4), \fBvfstab\fR(4),
138 The command is run by a non-root user. Run as root.
148 The device name specified does not exist.
154 \fBnot a directory\fR
158 The specified mount point is not a directory.
164 \fBis not an udfs file system\fR
168 The device specified does not contain a udf 1.50 file system or the udfs file
169 system module is not available.
175 \fBis already mounted\fR
179 The specified device is already in use.
185 \fBnot a block device\fR
189 The device specified is not a block device. Use block device to mount.
195 \fBwrite-protected\fR
199 The device is read-only.
205 \fBis corrupted. needs checking\fR
209 The file system is in an inconsistent state. Run \fBfsck\fR.
215 Copy-protected files can be stored on \fBDVD-ROM\fR media using Universal Disk
216 Format (\fBUDF\fR). Reading these copy-protected files is not possible as this
217 involves an authentication process. Unless an authentication process between
218 the host and the drive is completed, reading these copy-protected files after
219 mounting and before the authentication process, returns an error.