hsfs(7fs) - osol9

1hsfs(7FS)                        File Systems                        hsfs(7FS)
2
3
4

NAME

6       hsfs - High Sierra & ISO 9660 CD-ROM file system
7

DESCRIPTION

9       HSFS  is  a  file system type that allows users to access files on High
10       Sierra or  ISO 9660 format CD-ROM disks from within the SunOS operating
11       system.  Once mounted, a HSFS file system provides standard SunOS read-
12       only file system operations and semantics, meaning that  you  can  read
13       and  list  files in a directory on a High Sierra or ISO 9660 CD-ROM and
14       applications can use standard UNIX system  calls  on  these  files  and
15       directories.
16
17
18       This  file  system  contains support for Rock Ridge, ISO 9660 Version 2
19       and Joliet extensions. These extensions provide support for file  names
20       with  a   length  of at least 207 bytes, but only Rock Ridge extensions
21       (with the exception of writability and hard  links)  can  provide  file
22       system  semantics and file types as they are found in UFS. The presence
23       of Rock Ridge, ISO 9660 Version 2  and Joliet is autodetected  and  the
24       best-suitable  available extension is  used by the HSFS driver for file
25       name and attribute lookup.
26
27
28       If  your /etc/vfstab file contains a line similar to the following:
29
30         /dev/dsk/c0t6d0s0 −/hsfs hsfs -no ro
31
32
33
34       and /hsfs exists, you can mount an HSFS file system with either of  the
35       following commands:
36
37         mount -F hsfs -o ro device-special directory-name
38
39
40
41       or
42
43         mount /hsfs
44
45
46
47       By default, Rock Ridge extensions are used if available, otherwise  ISO
48       9660 Version 2, then Joliet are used. If neither extension  is  present
49       HSFS  defaults  to  the  standard  capabilities of ISO  9660. Since so-
50       called hybrid CD-ROMs that contain multiple  extensions  are  possible,
51       you  can  use  the  following mount options to deliberately disable the
52       search for a specific extension or to  force  the  use  of  a  specific
53       extension even if a preferable type is present:
54
55         mount -F hsfs -o ro,nrr device-special directory-name
56
57
58
59       Mount options are:
60
61
62       rr—request  HSFS  to use Rock Ridge extensions, if present. This is the
63       default  behavior and does not need to be explicitly specified.
64
65
66       nrr—disable detection  and  use  of  Rock  Ridge  extensions,  even  if
67       present.
68
69
70       vers2—request  HSFS  to use ISO 9660 Version 2 extensions, even if Rock
71       Ridge is available.
72
73
74       novers2—disable detection and use of ISO 9660 Version 2 extensions.
75
76
77       joliet—request HSFS to use Joliet extensions, even if Rock Ridge or ISO
78       9660 Version 2 extensions are available.
79
80
81       nojoliet—disable detection and use of Joliet extensions.
82
83
84       Files  on  a High Sierra or ISO 9660 CD-ROM disk have names of the form
85       filename.ext;version, where  filename and the optional  ext consist  of
86       a  sequence  of  uppercase  alphanumeric  characters (including ``_''),
87       while the version consists of a sequence of  digits,  representing  the
88       version number of  the file. HSFS converts all the uppercase characters
89       in a file name to lowercase, and truncates the ``;'' and version infor‐
90       mation.  If  more than one version of a file is present on the  CD-ROM,
91       only the file with the highest version number is accessible.
92
93
94       Conversion of uppercase to lowercase  characters  may  be  disabled  by
95       using the -o nomaplcase option to mount(1M). (See mount_hsfs(1M)).
96
97
98       If  the   CD-ROM  contains  Rock  Ridge,  ISO  9660 version 2 or Joliet
99       extensions, the file names and directory names may contain any  charac‐
100       ter supported under  UFS. The names may also be upper and/or lower case
101       and are case sensitive. File name lengths can be as long  as  those  of
102       UFS.
103
104
105       Files accessed through HSFS have mode 555 (owner, group and world read‐
106       able and executable),  uid 0 and gid 3. If a directory  on  the  CD-ROM
107       has  read  permission, HSFS grants execute permission to the directory,
108       allowing it to be searched.
109
110
111       With Rock Ridge extensions, files and directories can have any  permis‐
112       sions  that  are  supported  on  a  UFS file system. However, under all
113       write permissions, the file system is read-only, with EROFS returned to
114       any write operations.
115
116
117       Like High Sierra and ISO 9660 CD-ROMs, HSFS supports only regular files
118       and directories. A Rock Ridge CD-ROM can support regular files,  direc‐
119       tories,  and  symbolic  links,  as well as device nodes, such as block,
120       character, and FIFO.
121

EXAMPLES

123       Example 1 Sample Display of File System Files
124
125
126       If there is a file BIG.BAR on a High Sierra or ISO 9660  format  CD-ROM
127       it will show up as big.bar when listed on a HSFS file system.
128
129
130
131       If there are three files
132
133
134         BAR.BAZ;1
135
136
137         BAR.BAZ;2
138
139
140
141       and
142
143
144         BAR.BAZ;3
145
146
147
148       on  a  High  Sierra  or ISO 9660 format CD-ROM, only the file BAR.BAZ;3
149       will be accessible. It will be listed as bar.baz.
150
151

DIAGNOSTICS

168       hsfs: Warning: the file system...
169       does not conform to the ISO-9660 spec
170
171           The  specific  reason  appears  on the following line. You might be
172           attempting to mount a CD-ROM containing a  different  file  system,
173           such as UFS.
174
175
176       hsfs: Warning: the file system...
177       contains a file [with an] unsupported type
178
179           The  hsfs  file  system does not support the format of some file or
180           directory on the CD-ROM, for example a record structured file.
181
182
183       hsfs: hsnode table full, %d nodes allocated
184
185           There are not enough HSFS internal data structure elements to  han‐
186           dle  all the files currently open.  This problem may be overcome by
187           adding a line of the form set hsfs:nhsnode=number to the  /etc/sys‐
188           tem system configuration file and rebooting.  See system(4).
189
190

WARNINGS

192       Do not physically eject a CD-ROM while the device is still mounted as a
193       HSFS file system.
194
195
196       Under MS-DOS (for which CD-ROMs are frequently targeted), files with no
197       extension may be represented either as:
198
199         filename.
200
201
202
203       or
204
205         filename
206
207
208
209       that is, with or without a trailing period. These names are not equiva‐
210       lent under UNIX systems. For example, the names:
211
212         BAR.
213
214
215
216       and
217
218         BAR
219
220
221
222       are not names for the same file under the UNIX system. This  may  cause
223       confusion  if  you  are consulting documentation for CD-ROMs originally
224       intended for MS-DOS systems.
225
226
227       Use of the -o notraildot option to mount(1M) makes it optional to spec‐
228       ify the trailing dot. (See mount_hsfs(1M)).
229

NOTES

231       No  translation  of  any sort is done on the contents of High Sierra or
232       ISO 9660 format CD-ROMs; only directory and file names are  subject  to
233       interpretation by HSFS.
234
235
236
237SunOS 5.11                        1 Nov 2006                         hsfs(7FS)

NAME

DESCRIPTION

EXAMPLES

SEE ALSO

DIAGNOSTICS

WARNINGS

NOTES