Mount a block special device or remote filesystem
mount [-abwruv] [-t type [-o options] [special] mountpoint] mount [-abwruv] [-T type [-o options] special [mountpoint]] mount [-abwruv] -e [-t|T type] [-o options] special [mountpoint] mount
For more information, see “Ordering mountpoints” in the Process Manager chapter of the System Architecture guide.
|type:||Filesystem or manager:|
|etfs||Embedded Transaction Filesystem (e.g. fs-etfs-ram)|
|io-pkt||io-pkt-v4, io-pkt-v4-hc, io-pkt-v6-hc|
If you don't specify the filesystem, mount tries to determine which to use. If it can't figure out which to use, it uses qnx4.
|Specify io-pkt for type no matter which of io-pkt-v4, io-pkt-v4-hc, or io-pkt-v6-hc you're mounting.|
Without options, mount displays the current mountpoints. 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.
|Some servers may not support all the mount options, especially with respect to remounting and enumerating.|
The mount utility supports the /etc/fstab file.
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-pkt*. In this example, devn-ne2000.so is the name of the shared object that io-pkt* needs to load for the driver, not the name of a real device:
mount -T io-pkt devn-ne2000.so
If you want to pass options to the driver, use the -o option before the name of the shared object:
mount -T io-pkt -o mac=12345678 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:188.8.131.52:/C /ctest
Where your name is abc, your password is efg, your CIFS server is node123 with an IP address of 184.108.40.206, 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-pkt /lib/dll/lsm-qnet.so
Display the current mountpoints:
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
Remount the filesystem that's currently mounted at / as read-only:
mount -ur /
Remount the filesystem that's currently mounted at / as read-write:
mount -uw /
devb-*, fdisk, fs-cd.so, fs-cifs, fs-dos.so, fs-etfs-ram, fs-ext2.so, fs-mac.so, fs-nfs2, fs-nfs3, fs-nt.so, fs-qnx4.so, fs-qnx6.so, fs-udf.so, /etc/fstab, io-audio, io-blk.so, io-pkt*, io-usb, umount
mount(), mount_parse_generic_args() in the QNX Neutrino Library Reference
Filesystems chapter of the System Architecture guide
Working with Filesystems chapter, and “Filesystems and block I/O (devb-*) drivers” in the Fine-Tuning Your System chapter of the QNX Neutrino User's Guide