1mount_hsfs(1M) System Administration Commands mount_hsfs(1M)
2
6 mount_hsfs - mount hsfs file systems
7
9 mount -F hsfs [generic_options]
10 [-o FSType-specific_options] [-O ] special | mount_point
11 mount -F hsfs [generic_options]
14 [-o FSType-specific_options] [-O] special mount_point
15
18 mount attaches an ISO 9660 filesystem (the High Sierra file system,
19 hsfs, is a draft predecessor to ISO 9660, so the name reflects the
20 filesystem's history) to the file system hierarchy at the
21 mount_point, which is the pathname of a directory. If mount_point has
22 any contents prior to the mount operation, these are hidden until the
23 file system is unmounted.
24 If mount is invoked with special or mount_point as the only argu‐
27 ments, mount will search /etc/vfstab to fill in the missing argu‐
28 ments, including the FSType-specific_options; see mount(1M) for more
29 details.
30 The hsfs file system supports direct mounting of files containing the
33 file system as well as block devices. See mount(1M) and lofiadm(1M).
34 A file system conforming to ISO 9660 can contain extensions that allow
37 it to overcome limitations of the original ISO 9660:1988 (version 1)
38 standard. The following types of extensions are supported by hsfs:
39 Rock Ridge extensions
41 This is the preferred type of extension as it allows file
43 attributes, name length, and types equivalent to those on other
44 UNIX-style filesystems. Example of supported features are device
45 special files, POSIX permissions, symbolic links, and filenames of
46 up to 255 bytes in length. Rock Ridge extensions also remove the
47 ISO9660:1988 restriction on maximum nesting depth for directories
48 (eight levels). hsfs automatically detects the presence of Rock
49 Ridge extensions and uses them, unless mount options are specified
50 to disable the use of Rock Ridge or to use a different extension.
51 ISO9660:1999 (version 2) extensions
54 The first version of ISO9660, released in 1988, supported only
56 uppercase ASCII filenames of no more than 31 characters in length.
57 ISO9660 version 2, released in 1999, provides an extension that
58 allows filenames of at least 207 bytes that can use UTF-8 charac‐
59 ters and removes the limitation on the nesting depth for directo‐
60 ries. Unlike Rock Ridge, it does not provide support for UNIX-
61 style file types and file attributes. hsfs automatically detects
62 this extension and will use it for filename lookup if no Rock Ridge
63 extensions are found on the media.
64 Joliet extensions
67 The Joliet extension was devised by Microsoft to allow Unicode
69 (UCS-2) long filenames with CDROM-based media. It allows filename
70 lengths of up to 110 Unicode characters and does not support UNIX-
71 style file types and attributes. hsfs falls back to using Joliet if
72 such an extension is present and neither Rock Ridge nor ISO9660
73 version 2 extensions are found.
74 If filenames are longer than the 64 UCS-2 characters officially
76 allowed by Microsoft (that is, 110 Unicode characters), they can
77 translate to up to 330 UTF-8 octets. Filenames that translate to
78 more than 255 UTF-8 octets will be truncated.
79
82 generic_options
83 See mount(1M) for the list of supported options.
85 -o
88 Specify hsfs file system specific options. If invalid options are
90 specified, a warning message is printed and the invalid options are
91 ignored. The following options are available:
92 global | noglobal
94 If global is specified and supported on the file system, and
96 the system in question is part of a cluster, the file system
97 will be globally visible on all nodes of the cluster. If
98 noglobal is specified, the mount will not be globally visible.
99 The default behavior is noglobal.
100 ro
103 Mount the file system read-only. This option is required.
105 rr | nrr
108 Enable (rr) or disable (nrr) the use of Rock Ridge. rr is the
110 default and need not be specified. If you use nrr and Rock
111 Ridge extensions are present in the file system, ignore them
112 and search for other available extensions or fall back to plain
113 ISO9660.
114 vers2 | novers2
117 Enable or disable the use of ISO9660 version 2 extensions. If
119 vers2 is specified and ISO9660 version 2 extensions are avail‐
120 able, hsfs will use ISO9660 version 2 even if the file system
121 contains the preferred Rock Ridge extensions as well. If
122 novers2 is specified, it will fall back to using either Joliet
123 extensions or plain ISO9660 even if ISO9660 version 2 exten‐
124 sions are available.
125 joliet | nojoliet
128 Enable or disable the use of Joliet extensions. If joliet is
130 specified and Joliet extensions are available, hsfs will use
131 them even if the file system contains the preferred Rock Ridge
132 and/or ISO9660 version 2 extensions. If nojoliet is specified,
133 it will fall back to using plain ISO9660.
134 notraildot
137 File names on High Sierra file systems consist of a proper name
139 and an extension separated by a '.' (dot) character. By
140 default, the separating dot is always considered part of the
141 file's name for all file access operations, even if there is no
142 extension present. Specifying notraildot makes it optional to
143 specify the trailing dot to access a file whose name lacks an
144 extension.
145 Exceptions: This option is effective only on file systems for
147 which Rock Ridge, ISO9660 version 2 or Joliet extensions are
148 not active, either because they are not present on the CD-ROM,
149 or they have been deliberately disabled via the nrr, novers2
150 and nojoliet option. If either extension is active, hsfs qui‐
151 etly ignores this option.
152 nomaplcase
155 File names on High Sierra/ISO9660 CD-ROMs with no extensions
157 present should be uppercase characters only. By default, hsfs
158 maps file names read from a non-Rock Ridge disk to all lower‐
159 case characters. nomaplcase turns off this mapping. The excep‐
160 tions for notraildot discussed above apply to nomaplcase.
161 -O
165 Overlay mount. Allow the file system to be mounted over an exist‐
167 ing mount point, making the underlying file system inaccessible.
168 If a mount is attempted on a preexisting mount point without set‐
169 ting this flag, the mount will fail, producing the error: device
170 busy.
171
174 Example 1 Mounting and Unmounting a DVD Image Directly
175 The following commands mount and unmount a DVD image.
178 # mount -F hsfs /images/solaris.iso /mnt/solaris-image
181 # umount /mnt/solaris-image
182
186 /etc/mnttab
187 table of mounted file systems
189 /etc/vfstab
192 list of default parameters for each file system
194
197 See attributes(5) for descriptions of the following attributes:
198 ┌─────────────────────────────┬─────────────────────────────┐
203 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
204 ├─────────────────────────────┼─────────────────────────────┤
205 │Availability │SUNWcsu │
206 └─────────────────────────────┴─────────────────────────────┘
207
209 lofiadm(1M), mount(1M), mountall(1M), mount(2), mnttab(4), vfstab(4),
210 attributes (5)
211
213 If the directory on which a file system is to be mounted is a symbolic
214 link, the file system is mounted on the directory to which the symbolic
215 link refers, rather than on top of the symbolic link itself.
216SunOS 5.11 29 May 2008 mount_hsfs(1M)