2

mount:

 -t, --types vfstype
              The argument following the -t is used to indicate the filesystem type.  The filesystem
              types which are currently supported include: adfs, affs, autofs, cifs, coda, coherent,
              cramfs, debugfs, devpts, efs, ext, ext2, ext3, ext4, hfs, hfsplus, hpfs, iso9660, jfs,
              minix, msdos, ncpfs, nfs, nfs4, ntfs, proc, qnx4, ramfs,  reiserfs,  romfs,  squashfs,
              smbfs,  sysv,  tmpfs,  ubifs,  udf, ufs, umsdos, usbfs, vfat, xenix, xfs, xiafs.  Note
              that coherent, sysv and xenix are equivalent and  that  xenix  and  coherent  will  be
              removed  at  some  point in the future — use sysv instead. Since kernel version 2.1.21
              the types ext and xiafs do not exist anymore. Earlier, usbfs was  known  as  usbdevfs.
              Note, the real list of all supported filesystems depends on your kernel.


              The  programs mount and umount support filesystem subtypes.  The subtype is defined by
              ’.subtype’ suffix.  For example  ’fuse.sshfs’. It’s recommended to use  subtype  nota-
              tion  rather  than add any prefix to the mount source (for example ’sshfs#example.com’
              is depreacated).


              For most types all the mount program has to do is issue a simple mount(2) system call,
              and no detailed knowledge of the filesystem type is required.  For a few types however
              (like nfs, nfs4, cifs, smbfs, ncpfs) ad hoc code is necessary. The  nfs,  nfs4,  cifs,
              smbfs, and ncpfs filesystems have a separate mount program. In order to make it possi-

              ble  to  treat  all  types  in  a  uniform  way,  mount  will  execute   the   program

If  no  -t  option is given, or if the auto type is specified, mount will try to guess
              the desired type.  Mount uses the blkid or volume_id library for guessing the filesys-
              tem  type;  if  that  does not turn up anything that looks familiar, mount will try to
              read the file /etc/filesystems, or, if that does not exist, /proc/filesystems.  All of
              the  filesystem  types  listed  there will be tried, except for those that are labeled
              "nodev" (e.g., devpts, proc and nfs).  If /etc/filesystems ends in a line with a  sin-
              gle * only, mount will read /proc/filesystems afterwards.


              The  auto type may be useful for user-mounted floppies.  Creating a file /etc/filesys-
              tems can be useful to change the probe order (e.g., to try vfat before msdos  or  ext3
              before  ext2)  or  if you use a kernel module autoloader.  Warning: the probing uses a
              heuristic (the presence  of  appropriate  ‘magic’),  and  could  recognize  the  wrong
              filesystem  type,  possibly  with catastrophic consequences. If your data is valuable,
              don’t ask mount to guess.


              More than one type may be specified in a comma separated list.  The list of filesystem
              types  can  be  prefixed  with  no  to specify the filesystem types on which no action
              should be taken.  (This can be meaningful with the -a option.) For example,  the  com-
              mand:


                     mount -a -t nomsdos,ext

mounts all filesystems except those of type msdos and ext.

O, --test-opts opts
              Used  in  conjunction  with  -a,  to  limit  the set of filesystems to which the -a is
              applied.  Like -t in this regard except that it is useless except in  the  context  of
              -a.  For example, the command:


                     mount -a -O no_netdev


              mounts  all  filesystems  except  those which have the option _netdev specified in the
              options field in the /etc/fstab file.


              It is different from -t in that each option is matched exactly; a leading  no  at  the
              beginning of one option does not negate the rest.


              The -t and -O options are cumulative in effect; that is, the command


                     mount -a -t ext2 -O _netdev


              mounts  all  ext2  filesystems  with  the _netdev option, not all filesystems that are
              either ext2 or have the _netdev option specified.

 -r, --read-only
              Mount the filesystem read-only. A synonym is -o ro.


              Note that, depending on the filesystem type, state and kernel behavior, the system may
              still  write  to  the device. For example, Ext3 or ext4 will replay its journal if the
              filesystem is dirty. To prevent this kind of write access, you may want to mount  ext3
              or ext4 filesystem with "ro,noload" mount options or set the block device to read-only
              mode, see command blockdev(8).


       -w, --rw
              Mount the filesystem read/write. This is the default. A synonym is -o rw.


       -L label
              Mount the partition that has the specified label.

user   Allow  an  ordinary  user  to  mount the filesystem.  The name of the mounting user is
              written to mtab so that he can unmount the filesystem again.  This option implies  the
              options  noexec, nosuid, and nodev (unless overridden by subsequent options, as in the
              option line user,exec,dev,suid).