2 .\" Copyright 1989 AT&T 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_HSFS 8 "May 29, 2008"
8 mount_hsfs \- mount hsfs file systems
12 \fBmount\fR \fB-F\fR hsfs [\fIgeneric_options\fR]
13 [\fB-o\fR \fIFSType-specific_options\fR] [\fB-O\fR ] \fIspecial\fR | \fImount_point\fR
18 \fBmount\fR \fB-F\fR hsfs [\fIgeneric_options\fR]
19 [\fB-o\fR \fIFSType-specific_options\fR] [\fB-O\fR] \fIspecial\fR \fImount_point\fR
25 \fBmount\fR attaches an ISO 9660 filesystem (the High Sierra file system,
26 \fBhsfs\fR, is a draft predecessor to ISO 9660, so the name reflects the
27 filesystem's history) to the file system hierarchy at the \fImount_point\fR,
28 which is the pathname of a directory. If \fImount_point\fR has any contents
29 prior to the mount operation, these are hidden until the file system is
33 If \fBmount\fR is invoked with \fIspecial\fR or \fImount_point\fR as the
34 only arguments, \fBmount\fR will search \fB/etc/vfstab\fR to fill in the
35 missing arguments, including the \fIFSType-specific_options\fR; see
36 \fBmount\fR(8) for more details.
39 The \fBhsfs\fR file system supports direct mounting of files containing the
40 file system as well as block devices. See \fBmount\fR(8) and
44 A file system conforming to ISO 9660 can contain extensions that allow it to
45 overcome limitations of the original ISO 9660:1988 (version 1) standard. The
46 following types of extensions are supported by \fBhsfs\fR:
50 \fBRock Ridge extensions\fR
54 This is the preferred type of extension as it allows file attributes, name
55 length, and types equivalent to those on other UNIX-style filesystems. Example
56 of supported features are device special files, POSIX permissions, symbolic
57 links, and filenames of up to 255 bytes in length. Rock Ridge extensions also
58 remove the ISO9660:1988 restriction on maximum nesting depth for directories
59 (eight levels). \fBhsfs\fR automatically detects the presence of Rock Ridge
60 extensions and uses them, unless mount options are specified to disable the use
61 of Rock Ridge or to use a different extension.
67 \fBISO9660:1999 (version 2) extensions\fR
71 The first version of ISO9660, released in 1988, supported only uppercase ASCII
72 filenames of no more than 31 characters in length. ISO9660 version 2, released
73 in 1999, provides an extension that allows filenames of at least 207 bytes
74 that can use UTF-8 characters and removes the limitation on the nesting depth
75 for directories. Unlike Rock Ridge, it does not provide support for UNIX-style
76 file types and file attributes. \fBhsfs\fR automatically detects this extension
77 and will use it for filename lookup if no Rock Ridge extensions are found on
84 \fBJoliet extensions\fR
88 The Joliet extension was devised by Microsoft to allow Unicode (UCS-2) long
89 filenames with CDROM-based media. It allows filename lengths of up to 110
90 Unicode characters and does not support UNIX-style file types and attributes.
91 \fBhsfs\fR falls back to using Joliet if such an extension is present and
92 neither Rock Ridge nor ISO9660 version 2 extensions are found.
94 If filenames are longer than the 64 UCS-2 characters officially allowed by
95 Microsoft (that is, 110 Unicode characters), they can translate to up to 330
96 UTF-8 octets. Filenames that translate to more than 255 UTF-8 octets will be
104 \fB\fIgeneric_options\fR\fR
108 See \fBmount\fR(8) for the list of supported options.
118 Mount the file system read-only. This option is required.
124 \fB\fBrr\fR | \fBnrr\fR\fR
128 Enable (\fBrr\fR) or disable (\fBnrr\fR) the use of Rock Ridge. \fBrr\fR is the
129 default and need not be specified. If you use \fBnrr\fR and Rock Ridge
130 extensions are present in the file system, ignore them and search for other
131 available extensions or fall back to plain ISO9660.
137 \fB\fBvers2\fR | \fBnovers2\fR\fR
141 Enable or disable the use of ISO9660 version 2 extensions. If \fBvers2\fR is
142 specified and ISO9660 version 2 extensions are available, \fBhsfs\fR will use
143 ISO9660 version 2 even if the file system contains the preferred Rock Ridge
144 extensions as well. If \fBnovers2\fR is specified, it will fall back to using
145 either Joliet extensions or plain ISO9660 even if ISO9660 version 2 extensions
152 \fB\fBjoliet\fR | \fBnojoliet\fR\fR
156 Enable or disable the use of Joliet extensions. If \fBjoliet\fR is specified
157 and Joliet extensions are available, \fBhsfs\fR will use them even if the file
158 system contains the preferred Rock Ridge and/or ISO9660 version 2 extensions.
159 If \fBnojoliet\fR is specified, it will fall back to using plain ISO9660.
165 \fB\fBnotraildot\fR\fR
169 File names on High Sierra file systems consist of a proper name and an
170 extension separated by a '.' (dot) character. By default, the separating dot
171 is always considered part of the file's name for all file access operations,
172 even if there is no extension present. Specifying \fBnotraildot\fR makes it
173 optional to specify the trailing dot to access a file whose name lacks an
176 \fBExceptions:\fR This option is effective only on file systems for which Rock
177 Ridge, ISO9660 version 2 or Joliet extensions are not active, either because
178 they are not present on the CD-ROM, or they have been deliberately disabled via
179 the \fBnrr\fR, \fBnovers2\fR and \fBnojoliet\fR option. If either extension is
180 active, \fBhsfs\fR quietly ignores this option.
186 \fB\fBnomaplcase\fR\fR
190 File names on High Sierra/ISO9660 CD-ROMs with no extensions present should be
191 uppercase characters only. By default, \fBhsfs\fR maps file names read from a
192 \fBnon-Rock Ridge\fR disk to all lowercase characters. \fBnomaplcase\fR turns
193 off this mapping. The exceptions for \fBnotraildot\fR discussed above apply to
206 Overlay mount. Allow the file system to be mounted over an existing mount
207 point, making the underlying file system inaccessible. If a mount is attempted
208 on a preexisting mount point without setting this flag, the mount will fail,
209 producing the error: \f(CWdevice busy\fR.
214 \fBExample 1 \fRMounting and Unmounting a DVD Image Directly
217 The following commands mount and unmount a DVD image.
222 # \fBmount -F hsfs /images/solaris.iso /mnt/solaris-image\fR
223 # \fBumount /mnt/solaris-image\fR
232 \fB\fB/etc/mnttab\fR\fR
236 table of mounted file systems
242 \fB\fB/etc/vfstab\fR\fR
246 list of default parameters for each file system
252 \fBlofiadm\fR(8), \fBmount\fR(8), \fBmountall\fR(8), \fBmount\fR(2),
253 \fBmnttab\fR(4), \fBvfstab\fR(4), \fBattributes\fR(5)
257 If the directory on which a file system is to be mounted is a symbolic link,
258 the file system is mounted on the directory to which the symbolic link refers,
259 rather than on top of the symbolic link itself.