mount(8) [ultrix man page]
mount(8) System Manager's Manual mount(8) Name mount, umount - mount or unmount file systems Syntax /etc/mount [ options ] [ device ] [ directory ] /etc/umount [ options ] [ device ] [ directory ] Description This is a general description of the command. Additional descriptions are provided to define the syntax and options for the NFS and UFS file systems. Each invocation of the command announces to the system that a file system is present on the device device. The file system may be local or remote. File directory must exist as a directory file. It becomes the name of the newly mounted file system root. If invoked without arguments, prints the list of mounted file systems. Physically write-protected disks and magnetic tape file systems must be mounted read-only or an error will occur at mount time. General users can only mount file systems with certain restrictions. For example, the user, other than the superuser, performing the mount must own the directory directory. Furthermore, no users other than the superuser can execute or programs on the mounted file systems. In addition, users other than the superuser cannot access block or special character devices such as on the mounted file systems. The command announces to the system that the removable file system previously mounted on the specified directory is to be removed. Only the person who mounted a particular file system or the superuser can unmount the file system again. Options -a Reads the file and mounts, or unmounts, all file systems listed there. -f Fast unmount. The option has no meaning for local file systems and directories. However, for remote file system types (such as NFS), the option causes the client to unmount the remotely mounted file systems and directories without notifying the server. This can avoid the delay of waiting for acknowledgment from a server that is down. -o options Specifies a string that is passed to the kernel and used by the specific file system's mount routine in the kernel. For spe- cific options, refer to the file system-specific description, such as -r Indicates that the file system is to be mounted read only. To share a disk, each host must mount the file system with the -r option. -t type Specifies the type of file system is being mounted. When used with the option, the option mounts all file systems of the given type found in the file. For specific file system types, refer to the file system-specific description, such as -v Tells what did or did not happen. (Verbose flag) The options for are: -a Unmounts all mounted file systems. It may be necessary to execute twice to accomplish unmounting of all mounted file systems. -v Tells what did or did not happen. (Verbose flag) Restrictions Mounting corrupted file systems will crash the system. Files File systems information table See Also getmnt(2), mount(2), fstab(5), fsck(8), mount(8nfs), mount(8ufs) mount(8)
Check Out this Related Man Page
mount(8ufs) mount(8ufs) Name mount - mount the local ULTRIX File System (UFS) Syntax /etc/mount [ -t ufs -r ] [ options ] device directory Description The command announces to the system that a file system is present on the device device. The specified device must be a local device. The file directory must exist and it must be a directory. It becomes the name of the newly mounted file system. To further protect from system crashes, only file systems that have been cleanly checked by are mounted. In emergency situations, the superuser can override this requirement by using the option as shown below. General users can mount file systems with certain restrictions in addition to those listed in The file system must have the clean byte set. To ensure the clean byte is set, run the command on the file system first. You can also try the mount and if it fails, then run and then try the mount again. Note that the user must have execute permissions on the device. A successful ufs-mount may generate the following warning message: "Warning, device has exceeded xxx threshold, fsck(8) is advised" where xxx is which metric was exceeded to cause the clean byte timeout factor to reach zero. See for an explanation of the timeout algo- rithm. Physically write-protected disks and magnetic tape file systems must be mounted read only or an error will occur at mount time. Options See the reference page for a description of the -t option. -o options Specifies options as a sequence of comma-separated words from the list below. force The superuser can force the mounting of unclean file systems. You should use the flag only in single-user mode when repairing or recovering damaged file systems. nodev Block and character special devices cannot be accessed from this file system. If you are concerned with nfs secu- rity, all ufs file systems that will be exported via nfs should be ufs mounted with the option. noexec Binaries cannot be executed from this file system. nosuid The and programs may not be executed from this file system. If you are concerned with nfs security, all ufs file systems that will be exported via nfs with the option specified in the file should be ufs mounted with the nosuid option. pgthresh=## Set the paging threshold for this file system in kilobytes. The default is 64 kilobytes. sync All writes are immediately written to disk (synchronously) as well as to the buffer cache. For the option to be meaningful, the file system must be mounted with write permissions. -r Mounts the device on directory read only. Restrictions The command should only be invoked by the command. Users (and superusers) should not invoke the command. Examples The command calls to do its work and is the preferred interface. A sample command is: # mount -t ufs -o nodev,nosuid,noexec,pgthresh=100 /dev/ra0g /usr Files UFS-specific mount program See Also getmnt(2), mount(2), fsck(8), mount(8) mount(8ufs)