GC !__DragonFly__ section.
[dragonfly.git] / sbin / mount_cd9660 / mount_cd9660.8
CommitLineData
984263bc
MD
1.\" Copyright (c) 1993, 1994
2.\" The Regents of the University of California. All rights reserved.
3.\" All rights reserved.
4.\"
5.\" This code is derived from software donated to Berkeley by
6.\" Christopher G. Demetriou.
7.\"
8.\" Redistribution and use in source and binary forms, with or without
9.\" modification, are permitted provided that the following conditions
10.\" are met:
11.\" 1. Redistributions of source code must retain the above copyright
12.\" notice, this list of conditions and the following disclaimer.
13.\" 2. Redistributions in binary form must reproduce the above copyright
14.\" notice, this list of conditions and the following disclaimer in the
15.\" documentation and/or other materials provided with the distribution.
16.\" 3. All advertising materials mentioning features or use of this software
17.\" must display the following acknowledgement:
18.\" This product includes software developed by the University of
19.\" California, Berkeley and its contributors.
20.\" 4. Neither the name of the University nor the names of its contributors
21.\" may be used to endorse or promote products derived from this software
22.\" without specific prior written permission.
23.\"
24.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
25.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
26.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
27.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
28.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
29.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
30.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
31.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
32.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
33.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
34.\" SUCH DAMAGE.
35.\"
36.\" @(#)mount_cd9660.8 8.3 (Berkeley) 3/27/94
37.\" $FreeBSD: src/sbin/mount_cd9660/mount_cd9660.8,v 1.12.2.6 2003/02/24 00:56:41 trhodes Exp $
1de703da 38.\" $DragonFly: src/sbin/mount_cd9660/mount_cd9660.8,v 1.2 2003/06/17 04:27:33 dillon Exp $
984263bc
MD
39.\"
40.Dd March 27, 1994
41.Dt MOUNT_CD9660 8
42.Os
43.Sh NAME
44.Nm mount_cd9660
45.Nd mount an ISO-9660 file system
46.Sh SYNOPSIS
47.Nm
48.Op Fl begjrv
49.Op Fl o Ar options
50.Op Fl s Ar startsector
51.Ar special | node
52.Sh DESCRIPTION
53The
54.Nm
55utility attaches the ISO-9660 file system residing on the device
56.Pa special
57to the global file system namespace at the location indicated by
58.Pa node .
59This command is normally executed by
60.Xr mount 8
61at boot time.
62.Pp
63The options are as follows:
64.Bl -tag -width indent
65.It Fl b
66Relax checking for Supplementary Volume Descriptor Flags field
67which is set to a wrong value on some Joliet formatted disks.
68.It Fl e
69Enable the use of extended attributes.
70.It Fl g
71Do not strip version numbers on files.
72(By default, if there are files with different version numbers on the disk,
73only the last one will be listed.)
74In either case, files may be opened without explicitly stating a
75version number.
76.It Fl j
77Do not use any Joliet extensions included in the file system.
78.It Fl o
79Options are specified with a
80.Fl o
81flag followed by a comma separated string of options.
82See the
83.Xr mount 8
84man page for possible options and their meanings.
85The following cd9660 specific options are available:
86.Pp
87.Bl -tag -width "nostrictjoliet" -compact
88.It Cm extatt
89Same as
90.Fl e .
91.It Cm gens
92Same as
93.Fl g .
94.It Cm nojoliet
95Same as
96.Fl j .
97.It Cm norrip
98Same as
99.Fl r .
100.It Cm nostrictjoliet
101Same as
102.Fl b .
103.El
104.It Fl r
105Do not use any Rockridge extensions included in the file system.
106.It Fl s Ar startsector
107Start the file system at
108.Ar startsector .
109Normally, if the underlying device is a CD-ROM drive,
110.Nm
111will try to figure out the last track from the CD-ROM containing
112data, and start the file system there. If the device is not a CD-ROM,
113or the table of contents cannot be examined, the file system will be
114started at sector 0. This option can be used to override the behaviour.
115Note that
116.Ar startsector
117is measured in CD-ROM blocks, with 2048 bytes each. This is the same
118as for example the
119.Cm info
120command of
121.Xr cdcontrol 1
122is printing.
123It is possible to mount an arbitrary session of a multi-session CD by specifying
124the correct
125.Ar startsector
126here.
127.It Fl v
128Be verbose about the starting sector decisions made.
129.El
130.Sh EXAMPLES
131The following command can be used to mount a Kodak Photo-CD:
132.Pp
133.Dl "mount_cd9660 -o rw -v -s 0 /dev/cd0c /cdrom"
134.Sh SEE ALSO
135.Xr cdcontrol 1 ,
136.Xr mount 2 ,
137.Xr unmount 2 ,
138.Xr fstab 5 ,
139.Xr mount 8
140.Sh BUGS
141POSIX device node mapping is currently not supported.
142.Pp
143Version numbers are not stripped if Rockridge extensions are in use.
144In this case, accessing files that don't have Rockridge names without
145version numbers gets the one with the lowest version number and not
146the one with the highest.
147.Pp
148There is no ECMA support.
149.Sh HISTORY
150The
151.Nm
152utility first appeared in
153.Bx 4.4 .