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.Dd March 27, 1994 38.Dt MOUNT_CD9660 8 39.Os BSD 4 40.Sh NAME 41.Nm mount_cd9660 42.Nd mount an ISO-9660 filesystem 43.Sh SYNOPSIS 44.Nm mount_cd9660 45.Op Fl egrv 46.Op Fl o Ar options 47.Op Fl s Ar startsector 48.Ar special | node 49.Sh DESCRIPTION 50The 51.Nm 52command attaches the ISO-9660 filesystem residing on the device 53.Pa special 54to the global filesystem namespace at the location indicated by 55.Pa node . 56This command is normally executed by 57.Xr mount 8 58at boot time. 59.Pp 60The options are as follows: 61.Bl -tag -width indent 62.It Fl e 63Enable the use of extended attributes. 64.It Fl g 65Do not strip version numbers on files. 66(By default, if there are files with different version numbers on the disk, 67only the last one will be listed.) 68In either case, files may be opened without explicitly stating a 69version number. 70.It Fl o 71Options are specified with a 72.Fl o 73flag followed by a comma separated string of options. 74See the 75.Xr mount 8 76man page for possible options and their meanings. 77.It Fl r 78Do not use any Rockridge extensions included in the filesystem. 79.It Fl s Ar startsector 80Start the filesystem at 81.Ar startsector . 82Normally, if the underlying device is a CD-ROM drive, 83.Nm 84will try to figure out the last track from the CD-ROM containing 85data, and start the filesystem there. If the device is not a CD-ROM, 86or the table of contents cannot be examined, the filesystem will be 87started at sector 0. This option can be used to override the behaviour. 88Note that 89.Ar startsector 90is measured in CD-ROM blocks, with 2048 bytes each. This is the same 91as for example the 92.Cm info 93command of 94.Xr cdcontrol 8 95is printing. 96.It Fl v 97Be verbose about the starting sector decisions made. 98.El 99.Sh SEE ALSO 100.Xr mount 2 , 101.Xr unmount 2 , 102.Xr fstab 5 , 103.Xr cdcontrol 8 , 104.Xr mount 8 105.Sh BUGS 106POSIX device node mapping is currently not supported. 107.Pp 108Version numbers are not stripped if Rockridge extensions are in use. 109In this case, accessing files that don't have Rockridge names without 110version numbers gets the one with the lowest version number and not 111the one with the highest. 112.Pp 113There is no ECMA support. 114.Sh HISTORY 115The 116.Nm 117utility first appeared 118.Bx 4.4 . 119