Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ mount(1M) — A/UX 2.0

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

mountd(1M)

nfsd(1M)

fsmount(2)

unmount(2)

mount(3)

umount(3)

fstab(4)

mtab(4)




mount(1M) mount(1M)
NAME mount, umount - mount and dismount file systems SYNOPSIS /etc/mount [-p] /etc/mount -a [frv] [-t type] [-T type] /etc/mount [-frv] [-t type] [-T type] [-o options] device- file mount-point /etc/umount [-v] -h host /etc/umount -a[v] /etc/umount [-v] [device-file]... /etc/umount [-v] [mount-point]... DESCRIPTION mount enables access to the files and directories in a file system contained in the disk or disk partition referenced as device-file. The topmost directory of the add-on file sys- tem is attached to the directory tree at mount-point. The directory mount-point must already exist. It serves as the entry point for the newly-mounted file system for as long as the file system remains mounted. If any files or direc- tories had been placed below the mount-point directory be- fore mounting, they become hidden. If device-file is speci- fied as host:mount-point the file system type is assumed to be a network file system (NFS) that can be reached across the Ethernet network (see exports(4)). umount disables access to the files and directories in an add-on file system referenced through mount-point or device-file. mount and umount maintain a table of mounted file systems in /etc/mtab, described in mtab(4). If invoked without an ar- gument, mount displays the table. Note that since /etc/mtab can be modified by commands other than mount and umount, its contents may not accurately reflect what is actually mount- ed. If invoked with only device-file or mount-point, mount searches /etc/fstab for an entry whose device-file or mount-point field matches the given argument. For example, mount /usr and mount /dev/floppy0 April, 1990 1



mount(1M) mount(1M)
are shorthand for mount /dev/floppy0 /usr if the following line is in /etc/fstab: /dev/floppy0 /usr 5.2 rw 1 1 MOUNT FLAG OPTIONS The following flag options are interpreted by mount: -p Print the list of mounted file systems in a format suitable for use in /etc/fstab. -a Attempt to mount all the file systems described in /etc/fstab. In this case, device-file and mount-point are taken from /etc/fstab. If a type is specified with the -t or -T options, all of the file systems in /etc/fstab with that type are mounted. File systems are not necessarily mounted in the order listed in /etc/fstab. -f Fake a new /etc/mtab entry. This does not actually mount any file systems. -v Provide verbose output; mount displays a message indi- cating which file system is being mounted. -t or -T The next argument is the file system type. The accepted types are: 4.2 (UFS), 5.2 (SVFS), nfs, and pc; see fstab(4) for a description of the legal file system types. -o Specifies options, a list of comma-separated words from the following list. Some options are valid for all file system types, while others apply to a specific type only. options valid on all file systems (the default is rw, noquota) are: quota Enforce usage limits. noquota Do not enforce usage limits. rw Read/write. ro Read-only. suid Allow set-user-ID execution. 2 April, 1990



mount(1M) mount(1M)
nosuid Do not allow set-user-ID execution. options specific to nfs (NFS) file systems are: bg If the first mount attempt fails, retry in the background. fg Retry in the foreground. retry=n Set number of mount failure retries to n. rsize=n Set read buffer size to n bytes. wsize=n Set write buffer size to n bytes. timeo=n Set NFS timeout to n tenths of a second. retrans=n Set number of NFS retransmissions to n. port=n Set server IP port number to n. soft Return error if server doesn't respond. hard Retry request until server responds. The defaults are fg,retry=1,timeo=7,retrans=4,port=NFS_PORT,hard with defaults for rsize and wsize set by the kernel. The bg option causes mount to run in the background if mountd(1M) of the server does not respond. mount at- tempts each request retry=n times before giving up. Once the file system is mounted, each NFS request made in the kernel waits timeo=n tenths of a second for a response. If no response arrives, the timeout is mul- tiplied by 2, and the request is retransmitted. When retrans=n retransmissions have been sent with no reply, a soft mounted file system returns an error on the re- quest, and a hard mounted file system retries the re- quest. File systems that are mounted rw (read/write) should use the hard option. The number of bytes in a read or write request can be set with the rsize and wsize options. -r Mount the specified file system read-only. This is a shorthand for mount -o ro device-file mount-point Physically write-protected and magnetic-tape file sys- April, 1990 3



mount(1M) mount(1M)
tems must be mounted read-only, or errors will occur when access times are updated, whether or not any ex- plicit write is attempted. UMOUNT FLAG OPTIONS The following flag options are interpreted for unmounting a file system: -h Unmount all file systems listed in /etc/mtab that are remotely mounted from host. -a Attempts to unmount all the file systems currently mounted (listed in /etc/mtab). In this case, device- file is taken from /etc/mtab. -v Provide verbose output; umount displays a message indi- cating the file system being unmounted. EXAMPLES mount /dev/dsk/c0d0s2 /usr mounts a local disk. mount -at 5.2 mounts all System V.2 file systems. mount -t nfs serv:/usr/src /usr/src mounts remote file system. mount serv:/usr/src /usr/src mounts remote file system. mount -o hard serv:/usr/src /usr/src mounts remote file system, but with hard mount. mount -p > /etc/fstab saves current mount table state in /etc/fstab where it will continue to be available to assist with the automatic mount- ing and unmounting of file systems. FILES /etc/mount /etc/umount /etc/mtab /etc/fstab 4 April, 1990



mount(1M) mount(1M)
SEE ALSO mountd(1M), nfsd(1M), fsmount(2), unmount(2), mount(3), umount(3), fstab(4), mtab(4). BUGS Mounting file systems full of garbage crashes the system. 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 is mounted on top of the symbolic link itself. April, 1990 5

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026