!!Caution!! USB devices mount immediately to the filesystem.
Removable media
*nix needs a way to know that removable media, such as floppy disks, CD-ROMs, DVD-ROMs, USB drives, and more, has been placed into a drive, or needs to be removed from a drive.
The operating system can detect some of these items, like CD-ROMs, and cannot detect others, like floppy disks. When you add removable media to your filesystem you are mounting it, and mounting is done with the mount command. The act of removing the media is called 'unmounting' (see: umount).
The following table describes how Red Hat Enterprise Linux views the various devices.
| Media | Device | Default Mount Point |
| CD-ROM | /dev/cdrom | /media/cdrom |
| CD-Writer | /dev/cdrecorder | /media/cdrecorder
|
| Floppy disk | /dev/floppy | /media/floppy |
| | | /dev/fd0 |
| USB device | /dev/sda1 | /media/usbdisk |
| | /dev/sda4 | #first USB device |
If you aren't sure if your media is mounted, or where it's mounted, type df. This command will show you where to find it, if it's there.
- Mounting media:
mount -t [type] /device /mountpoint
- Un-mounting media:
umount /device - or - umount /mountpoint (for CDROMs type the command eject)
When you have mounted something as read-write, you must make sure to cleanly unmount it before removing the item. Not all data is written immediately to disk by the operating system. A clean unmount makes sure to flush all of that data onto the disk so you don't end up with corrupted files.
MOUNT(8) BSD System Manager's Manual MOUNT(8)
NAME
mount -- mount file systems
SYNOPSIS
mount [-adfruvw] [-t ufs | lfs | external_type]
mount [-dfruvw] special | node
mount [-dfruvw] [-o options] [-t ufs | lfs | external_type] special node
DESCRIPTION
The mount command calls the mount(2) system call to prepare and graft a
special device or the remote node (rhost:path) on to the file system tree
at the point node. If either special or node are not provided, the
appropriate information is taken from the fstab(5) file.
The system maintains a list of currently mounted file systems. If no
arguments are given to mount, this list is printed.
The options are as follows:
-a All the filesystems described in fstab(5) are mounted. Excep-
tions are those marked as ``noauto'' or are excluded by the -t
flag (see below).
-d Causes everything to be done except for the actual system call.
This option is useful in conjunction with the -v flag to deter-
mine what the mount command is trying to do.
-f Forces the revocation of write access when trying to downgrade a
filesystem mount status from read-write to read-only.
-o Options are specified with a -o flag followed by a comma sepa-
rated string of options. The following options are available:
async All I/O to the file system should be done asynchronously.
This can be somewhat dangerous with respect to losing
data when faced with system crashes and power outages.
This is also the default. It can be avoided with the
noasync option.
force The same as -f; forces the revocation of write access
when trying to downgrade a filesystem mount status from
read-write to read-only.
noasync
This filesystem should not force all I/O to be written
asynchronously.
noauto This filesystem should be skipped when mount is run with
the -a flag.
nodev Do not interpret character or block special devices on
the file system. This option is useful for a server that
has file systems containing special devices for architec-
tures other than its own.
noexec Do not allow execution of any binaries on the mounted
file system. This option is useful for a server that has
file systems containing binaries for architectures other
than its own.
nosuid Do not allow set-user-identifier or set-group-identifier
bits to take effect.
rdonly The same as -r; mount the file system read-only (even the
super-user may not write it).
sync All I/O to the file system should be done synchronously.
update The same as -u; indicate that the status of an already
mounted file system should be changed.
union Causes the namespace at the mount point to appear as the
union of the mounted filesystem root and the existing
directory. Lookups will be done in the mounted filesys-
tem first. If those operations fail due to a non-exis-
tent file the underlying directory is then accessed. All
creates are done in the mounted filesystem.
Any additional options specific to a filesystem type that is not
one of the internally known types (see the -t option) may be
passed as a comma separated list; these options are distinguished
by a leading ``-'' (dash). Options that take a value are speci-
fied using the syntax -option=value. For example, the mount com-
mand:
mount -t hfs -o nosuid,-w,-m=755 /dev/disk2s9 /tmp
causes mount to execute the equivalent of:
/sbin/mount_hfs -o nosuid -w -m 755 /dev/disk2s9 /tmp
-r The file system is to be mounted read-only. Mount the file sys-
tem read-only (even the super-user may not write it). The same
as the ``rdonly'' argument to the -o option.
-t ufs | lfs | external type
The argument following the -t is used to indicate the file system
type. The type ufs is the default. The -t option can be used to
indicate that the actions should only be taken on filesystems of
the specified type. More than one type may be specified in a
comma separated list. The list of filesystem types can be pre-
fixed with ``no'' to specify the filesystem types for which
action should not be taken. For example, the mount command:
mount -a -t nonfs,hfs
mounts all filesystems except those of type NFS and HFS.
If the type is not one of the internally known types, mount will
attempt to execute a program in /sbin/mount_XXX where XXX is
replaced by the type name. For example, nfs filesystems are
mounted by the program /sbin/mount_nfs.
-u The -u flag indicates that the status of an already mounted file
system should be changed. Any of the options discussed above
(the -o option) may be changed; also a file system can be changed
from read-only to read-write or vice versa. An attempt to change
from read-write to read-only will fail if any files on the
filesystem are currently open for writing unless the -f flag is
also specified. The set of options is determined by first
extracting the options for the file system from the fstab table,
then applying any options specified by the -o argument, and
finally applying the -r or -w option.
-v Verbose mode.
-w The file system object is to be read and write.
The options specific to NFS filesystems are described in the
mount_nfs(8) manual page.
FILES
/etc/fstab file system table
SEE ALSO
mount(2), fstab(5), mount_afp(8), mount_cd9660(8), mount_cddafs(8),
mount_devfs(8), mount_fdesc(8), mount_hfs(8), mount_msdos(8),
mount_nfs(8), mount_smbfs(8), mount_synthfs(8), mount_udf(8),
mount_volfs(8), mount_webdav(8), umount(8)
BUGS
It is possible for a corrupted file system to cause a crash.
HISTORY
A mount command appeared in Version 6 AT&T UNIX.
4th Berkeley Distribution June 16, 1994 4th Berkeley Distribution
Fascinating! I worked on a project* once that involved a complete rewrite of the command-line utility passwd in order to keep a number of system services including a .htpasswd file in sync with users account passwords. Mac OS X Hints noted this is made simple with Mac OS X Leopard (10.5) and Open Directory.
Media Temple labs has a private beta for what it’s calling Xserve-Virtual . This system has been added quickly added to my MT wish list along with the Django GridContainer which, perhaps I wont need if I move over to a full-on-mirror of my development environment using a virtual OS X Server.
A virtual Mac OS X Leopard Server running on a fully loaded cluster of Xserves virtualized using Parallels Server . I want one, … or three, … yeah that should be enough …. maybe four, for symmetry.
Having started my journey down the command-line with Fedora 3, I was excited to try out Fedora 9. The install completed with ease (the first time around) but once I logged onto the system and attempted to configure some of the system settings, my root password didn’t work.
Why? CAPS LOCK bit was set by default during the install process making a different root password.