specify the filesystem types on which no action should be taken. The
           prefix no has no effect when specified in an /etc/fstab entry.

           The prefix no can be meaningful with the -a option. For example, the
           command

           mount -a -t nomsdos,smbfs

           mounts all filesystems except those of type msdos and smbfs.

           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) an ad hoc code is necessary. The nfs, nfs4, cifs,
           smbfs, and ncpfs filesystems have a separate mount program. In order
           to make it possible to treat all types in a uniform way, mount will
           execute the program /sbin/mount.type (if that exists) when called
           with type type. Since different versions of the smbmount program
           have different calling conventions, /sbin/mount.smbfs may have to be
           a shell script that sets up the desired call.

       -U, --uuid uuid
           Mount the partition that has the specified uuid.

       -v, --verbose
           Verbose mode.

       -w, --rw, --read-write
           Mount the filesystem read/write. Read-write is the kernel default
           and the mount default is to try read-only if the previous mount(2)
           syscall with read-write flags on write-protected devices failed.

           A synonym is -o rw.

           Note that specifying -w on the command line forces mount to never
           try read-only mount on write-protected devices or already mounted
           read-only filesystems.

       -h, --help
           Display help text and exit.

       -V, --version
           Print version and exit.

FILESYSTEM-INDEPENDENT MOUNT OPTIONS
       Some of these options are only useful when they appear in the /etc/fstab
       file.

       Some of these options could be enabled or disabled by default in the
       system kernel. To check the current setting see the options in
       /proc/mounts. Note that filesystems also have per-filesystem specific
       default mount options (see for example tune2fs -l output for extN
       filesystems).

       The options nosuid, noexec, nodiratime, relatime, noatime, strictatime,
       and nosymfollow are interpreted only by the abstract VFS kernel layer
       and applied to the mountpoint node rather than to the filesystem itself.
       Try:

              findmnt -o TARGET,VFS-OPTIONS,FS-OPTIONS

       to get a complete overview of filesystems and VFS options.

       The read-only setting (ro or rw) is interpreted by VFS and the
       filesystem and depends on how the option is specified on the mount(8)
       command line. The default is to interpret it on the filesystem level.
       The operation "-o bind,remount,ro" is applied only to the VFS
       mountpoint, and operation "-o remount,ro" is applied to VFS and
       filesystem superblock. This semantic allows create a read-only
       mountpoint but keeps the filesystem writable from another mountpoint.

       Since v2.39 libmount can use a new kernel mount interface to set the VFS
       options recursive. For backward compatibility, this feature is not
       enabled by default, although recursive operation (e.g. rbind) has been
       requested. The new option argument "recursive" could be specified, for
       example:

              mount -orbind,ro=recursive,noexec=recursive,nosuid /foo /bar

       recursively binds filesystems from /foo to /bar, /bar, and all submounts
       will be read-only and noexec, but only /bar itself will be "nosuid". The
       "recursive" optional argument for VFS mount options is an EXPERIMENTAL
       feature.

       The following options apply to any filesystem that is being mounted (but
       not every filesystem actually honors them - e.g., the sync option today
       has