Caution: This version of this document is no longer maintained. For the latest documentation, see http://www.qnx.com/developers/docs.

mount

Mount a block special device or remote filesystem

Syntax:

mount [-wruv] [-t type [-o options] [special] mountpoint]
mount [-wruv] [-T type [-o options] special [mountpoint]]
mount [-wruv] -e [-t|T type] [-o options] special
      [mountpoint]
mount

Runs on:

Neutrino

Options:

-b
Prevent the lookup of the fstab file.
-e
Enumerate the children of the special device.
-o options
Options specific to the server doing the mounting. These options include:

For more information, see "Ordering mountpoints" in the Process Manager chapter of the System Architecture guide.

-r
Mount the device as read-only.
-T type ... special [mountpoint]
The special device is a string that may specify a real device or may be just a hint for the server. If mountpoint isn't specified, the server will automatically create an appropriate mountpoint.
-t type ... [special] mountpoint
If the optional special string is given, the mount request goes to the server which created, or is responsible for, the special device. If this special device does not exist, the server interprets the string as a hint. If special is not given, it is passed as NULL.
-u
Mount for update (remount).
-v
Increase the verbosity.
-w
Mount the device as read/write.
mountpoint
Where the device is to be mounted on your system.
special
The name of the special device.
type
The type of filesystem or manager to mount:
type: Filesystem or manager:
cd fs-cd.so
cifs fs-cifs
dos fs-dos.so
ext2 fs-ext2.so
io-audio io-audio
io-net io-net
io-usb io-usb
nfs fs-nfs2, fs-nfs3
qnx4 fs-qnx4.so

The default is qnx4.

Description:

Without options, mount displays the current mount points. With options set, this utility mounts the block special device or remote filesystem, special, as the specified mountpoint. To mount a real special device, use the -t option; to specify a special-device string (which isn't necessarily a real device), use -T.


Note: Some servers may not support all the mount options, especially with respect to remounting and enumerating.

The mount utility supports the /etc/fstab file.

Examples:

Mount a QNX 4 filesystem on a hard drive as /mnt/fs:

mount -t qnx4 /dev/hd0t77 /mnt/fs

Mount a device driver for io-net. In this example, devn-ne2000.so is the name of the shared object that io-net needs to load for the driver, not the name of a real device:

mount -T io-net devn-ne2000.so

Enumerate the hard disk partition table:

mount -e /dev/hd0

This will re-read the disk partition table for /dev/hd0, and create, update or delete /dev/hd0tXX block-special files for each partition. This is used in the following two scenarios:

Mount a CIFS filesystem (fs-cifs must be running first):

mount -T cifs -o abc,efg //node123:1.1.1.1:/C /ctest 

Where your name is abc, your password is efg, your CIFS server is node123 with an IP address of 1.1.1.1, the share you want to mount is /C, and the mountpoint you want to use is /ctest.

Mount an NFS 2 client filesystem (fs-nfs2 must be running first):

mount -T nfs 10.1.0.22:/home /mnt/home

Mount an NFS 3 client filesystem (fs-nfs3 must be running first):

mount -T nfs -o ver3 server_node:/qnx_bin /bin

Mount the Qnet network protocol:

mount -T io-net /lib/dll/npm-qnet.so

Display current mount points:

mount

Mount the shared object that supports Enhanced Host Controller Interface (EHCI) USB controllers:

mount -T io-usb devu-ehci.so /dev/io-usb/io-usb

See also:

fs-cd.so, fs-cifs, fs-dos.so, fs-ext2.so, fs-nfs2, fs-nfs3, fs-qnx4.so, /etc/fstab, io-audio, io-net, io-usb, umount