mount attaches a High Sierra file system (hsfs) to the file system hierarchy at the mount_point, which is the pathname of a directory. If mount_point has any contents prior to the mount operation, these are hidden until the file system is unmounted.
If mount is invoked with special or mount_point as the only arguments, mount will search /etc/vfstab to fill in the missing arguments, including the FSType-specific_options; see mount(1M) for more details.
If the file system being mounted contains Rock Ridge extensions, by default they will be used, enabling support of features not normally available under High Sierra file systems, such as symbolic links and special files.
Security attributes can be specified at mount time, either with the -o or -S option on the mount command line or in the vfstab_adjunct(4) file. See the DESCRIPTION in the mount(1M) man page for more about specifying security attributes.
To succeed, the mount command must have the
sys_mount privilege. Mandatory and discretionary read access are required to both the mount point and the device being mount; to override MAC and DAC restrictions requires privilege as described in Intro(2). To succeed in all cases, mount -F hsfs needs the
See mount(1M) for the list of supported options.
Specify hsfs file system specific options. Most attributes for the -S option may also be specified for the -o option. See the -S option.
If global is specified and supported on the file system, and the system in question is part of a cluster, the file system will be globally visible on all nodes of the cluster. If noglobal is specified, the mount will not be globally visible. The default behavior is noglobal.
Mount the file system read-only. This option is required.
no Rock Ridge: if Rock Ridge extensions are present in the file system, ignore them; interpret it as a regular High Sierra file system.
File names on High Sierra file systems consist of a proper name and an extension separated by a '.' (dot) character. By default, the separating dot is always considered part of the file's name for all file access operations, even if there is no extension present. Specifying notraildot makes it optional to specify the trailing dot to access a file whose name lacks an extension.
Exceptions: This option is effective only on file systems for which Rock Ridge extensions are not active, either because they are not present on the CD-ROM, or they are explicitly ignored via the nrr option. If Rock Ridge extensions are active, hsfs quietly ignores this option.
File names on High Sierra cdroms with no Rock Ridge extensions present should be uppercase characters only. By default, hsfs maps file names read from a non-Rock Ridge disk to all lowercase characters. nomaplcase turns off this mapping. The exceptions for notraildot discused above apply to nomaplcase.
By default the file system is mounted with setuid execution allowed. Specifying nosuid causes the file system to be mounted with setuid execution disallowed.
Allow (disallow) access to character and block devices. The default is devices.
Note: In the Trusted Solaris environment, device special files are typically located only in the /dev and /devices directories in the root file system. All other file systems should be mounted with the nodevices option to prevent recognition of devices that may reside in any other directories. The recognition of devices is also affected by the use of the devices or nodevices options to the share(1M) command, either on the command line or in the dfstab(4) file.
Forced privileges on executables are allowed or disallowed. The default is priv. The recognition of forced privileges is also affected by the use of the priv or nopriv option to the share(1M) command, either on the command line or in the dfstab(4) file.
Overlay mount. Allow the file system to be mounted over an existing mount point, making the underlying file system inaccessible. If a mount is attempted on a pre-existing mount point without setting this flag, the mount will fail, producing the error device busy.
See the DESCRIPTION and the attribute list on the mount(1M) man page.
The nodevices and nopriv options have been added. Trusted Solaris security policy applies when mounting and unmounting file systems.
Except when merely listing mounted file systems and resources, mount must run with the
Mandatory and discretionary read access is required to both the mount point and the device being mounted; to override MAC and DAC restrictions requires privilege as described in Intro(2). To succeed in all cases, mount -F hsfs needs the
Mount-time security attributes can be specified for file systems whose objects do not have any attributes (such as user and group IDs) and for file systems that do not have the Trusted Solaris extended security attributes (such as sensitivity labels). Specifying attributes fails for file systems and file system objects (files or directories) that already have a specified attribute. Trusted Solaris security policy applies when mounting. See the mount(1M) and vfstab_adjunct(4) man pages for more details.
Table of mounted file systems.
List of default parameters for each file system.
Mount-time attributes for file systems.
See attributes(5) for descriptions of the following attributes:
If the directory on which a file system is to be mounted is a symbolic link, the file system is mounted on the directory to which the symbolic link refers, rather than on top of the symbolic link itself.