Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

mount_cd9660(8) [osx man page]

MOUNT_CD9660(8) 					    BSD System Manager's Manual 					   MOUNT_CD9660(8)

NAME
mount_cd9660 -- mount an ISO-9660 filesystem SYNOPSIS
mount_cd9660 [-egjr] [-o options] [-s startsector] special node DESCRIPTION
The mount_cd9660 command attaches the ISO-9660 filesystem residing on the device special to the global filesystem namespace at the location indicated by node. This command is normally executed by mount(8) at boot time. The options are as follows: -e Enable the use of extended attributes. -g Do not strip version numbers on files. (By default, if there are files with different version numbers on the disk, only the last one will be listed.) In either case, files may be opened without explicitly stating a version number. -j Do not use any Joliet extensions included in the filesystem. -o Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. -r Do not use any Rockridge extensions included in the filesystem. -s startsector Start the filesystem at startsector. Normally, if the underlying device is a CD-ROM drive, mount_cd9660 will try to figure out the last track from the CD-ROM containing data, and start the filesystem there. If the device is not a CD-ROM, or the table of contents cannot be examined, the filesystem will be started at sector 0. This option can be used to override the behaviour. Note that startsector is measured in CD-ROM blocks, with 2048 bytes each. SEE ALSO
mount(2), unmount(2), fstab(5), mount(8) BUGS
POSIX device node mapping is currently not supported. Version numbers are not stripped if Rockridge extensions are in use. In this case, accessing files that don't have Rockridge names without version numbers gets the one with the lowest version number and not the one with the highest. There is no ECMA support. HISTORY
The mount_cd9660 utility first appeared 4.4BSD. 4th Berkeley Distribution March 27, 1994 4th Berkeley Distribution

Check Out this Related Man Page

MOUNT_ADOS(8)						    BSD System Manager's Manual 					     MOUNT_ADOS(8)

NAME
mount_ados -- mount an AmigaDOS file system SYNOPSIS
mount_ados [-o options] [-u uid] [-g gid] [-m mask] special node DESCRIPTION
The mount_ados command attaches the AmigaDOS filesystem residing on the device special to the global filesystem namespace at the location indicated by node. Both special and node are converted to absolute paths before use. This command is normally executed by mount(8) at boot time, but can be used by any user to mount an AmigaDOS file system on any directory that they own (provided, of course, that they have appro- priate access to the device that contains the file system). The options are as follows: -o options Use the specified mount options, as described in mount(8). -u uid Set the owner of the files in the file system to uid. The default owner is the owner of the directory on which the file system is being mounted. -g gid Set the group of the files in the file system to gid. The default group is the group of the directory on which the file system is being mounted. -m mask Specify the maximum file permissions for files in the file system. (For example, a mask of 755 specifies that, by default, the owner should have read, write, and execute permissions for files, but others should only have read and execute permissions. See chmod(1) for more information about octal file modes.) Only the nine low-order bits of mask are used. The default mask is taken from the directory on which the file system is being mounted. SEE ALSO
mount(2), unmount(2), fstab(5), mount(8) HISTORY
The mount_ados utility first appeared in NetBSD 1.0. BUGS
The 'ados' filesystem currently supports the Amiga fast file system. The 'ados' filesystem implementation currently is read-only. The mount_ados utility silently retries the mount read-only, as if the ro option were specified, when it encounters the [EROFS] error. BSD
April 7, 1994 BSD
Man Page