This program is used to mount and unmount file systems for GNOME
desktop users. It can also be used to eject discs from CD drives and
other devices that needs to be ejected. For example, iPod's needs this
to make the "Do not disconnect" message go away.
Normally, this program is invoked by software in the GNOME stack
). End users should never have to deal with gnome-mount directly
on the command line, nor should they have to read this manual
Mounting a file system into the root file system involves a certain
degree of configuration and as such is subject to whatever preferences
an user might have.
allows the user to control the mount point location, the mount options
and what file system to use for mounting a file system. The settings
are read from the
database (which is per-user) and can also be overridden on the command
line using the appropriate parameters. See below.
SPECIFYING THE TARGET
The target (e.g. the partition or file system to mount, unmount or
eject) can be specified using the
UDI (Unique Device Identifier), e.g.
, the name of the special device file, e.g.
or a pseudonym.
The latter is a textual string used to locate the target and it makes
search for the target by comparing the given textual string to the
mount points and file system labels.
Settings (e.g. mount point, mount options, file system type) are read
in the order below. Note that each option is treated individually; for
example it is valid for a drive to only specify the mount point
setting and not the mount options. Also note that the even if the
drive specifies mount options, these can be overridden on a per-volume
FILE SYSTEM DEFAULTS
First, default mount options are read from
for the probed file system type of the volume. The option
is treated specially by
and will be replaced by
to cope with the fact that the
is a function of the user calling it.
Second, the gconf tree at
is consulted for options that depend on what drive the volume belongs
to. For example, this is useful for configuring that volumes inserted
into a given drive is always mounted at the same location. For example,
this can be used to emulate
behaviour by where CD media is always mounted at e.g.
Third, the gconf tree at
is consulted for options that are specific to a particular piece of
media and as such depends on either the file system label (e.g.
) or the file system UUID (e.g.
) or both.
Users can pass
on the commandline to override settings.
EXTRA COMMANDLINE OPTIONS
Finally, if mount options are passed via
these are not replacing the mount options, they are simply added.
This is useful for doing e.g.
gnome-mount --extra-mount-options remount,exec -d /dev/sda1
to remount a volumes such that programs can be run from the media.
This is useful for e.g. gnome-volume-manager if it discovers an
autorun file on the media.
supports passworded media through the
interface supported by
and this includes volumes formatted in a way that adheres to the
(Linux Unified Key Setup) specification. In addition,
to retrieve and store the pass phrase. If no key can be retrieved,
will prompt the user for one. In addition, if the keyring is
locked, the user may be prompted to unlock it via standard
is intended for unprivileged users and
ultimately controls if the calling user is allowed to mount, unmount
or eject volumes as well as what mount options are valid. As such,
requests may be denied. See the (human readable) exception returned
for details if a request fails.
has a notion of what mount options are valid for a given volume. They
are listed in the HAL property
on the device object representing the volume to mount. Consult
for details. Also note that HAL by default appends the options
to prevent privilege escalation.
In addition to using
as the mechanism for mounting file systems, the
file is also consulted as
will refuse to mount any file system listed in this file as it would
violate system policy. If this is the case,
as the calling user rather than invoking the
method on the
interface on the device object representing the volume / drive. This
means that settings (mount point, mount options, file system type)
are not passed along as these are already specified in the
file and there are no mechanism to override them. When parsing the
for that matter)
resolves symbolic links and also respects the
notations. For example, if this line is in
LABEL=MyVolume /mnt/myvolume auto user,defaults 0 0
mounts the file system with the label MyVolume via
rather than using the
Options available for the
Verbose operation, shows debug messages.
Don't show any dialogs the user needs to dismiss. If X11 is
may pop up transient notification bubbles e.g. suggesting the user to
remount a volume with different options to streamline access to file
systems with ownership attributes. This is the option that storage
policy daemons such as
in. File managers, however, such as
, should never use this option as the user should get e.g. an error
dialog if he tries to access a volume with a missing, unsupported or
unknown file system.
to block even if an error occured. By default,
will daemonize so it can return control to the invoking application as
soon as possible (e.g. when an operation either fails or succeeds )
while still showing an error dialog to the end user. Useful when
Use this for unmounting rather than mounting. If
is invoked as
(a symlink to
) then this option is automatically selected.
Use this for ejecting rather than mounting. If
is invoked as
(a symlink to
) then this option is automatically selected.
Specify target volume by the special device file.
Specify target volume by
UDI (Unique Device Identifier).
Specify target volume by pseudonym. See above for how this works.
Never use X11 dialogs or notification bubbles even if an X11 server is
available. Also prohibits the use of
to retrieve pass phrases for passworded media because this might
require unlocking the keyring which happens through an X11 dialog
out of process. Useful for command line operation.
Specify mount point to use; don't include
as this is automatically appened by the mechanism used to mount,
Specify mount options. Separate by comma.
Specify file system type. This is useful for using e.g. the
file system instead of the
Instead of mounting a drive, specify what options to store in the
gconf database. Can be used on both drives and volumes. Be careful
using this with the
option as optical drives (among others) use the same special device
file for both the drive and the volume. One trick is to ensure the
optical drive has no media when configuring it via this option.
Another possibility is to use the
Display settings for a drive or volume.
Erase settings for a drive or volume.
will return zero if the request succeeded or non-zero if it
failed. Note that
is specifically designed to run in a graphical user environment and as
such all error reporting (and resolution) is through X11 dialogs. For
reports that a volume could not be mounted because of a missing
file system driver,
might, one day, launch a tool to ask the user if he wants to download
and install the driver. In a similar way, all error dialogs are
presented via X11 dialogs to the user as well.
We want to make sure that the discs inserted into an optical drive
are always mounted at
instead of using the default which is using the label specified in the
file system header. Assuming that the drive is empty and the special
device file for the drive is
the following command will work
This can be inspected via the
option and the settings can also be erased via the
option. Also note that
can be used for tasks like these.
HARDWARE THAT CANNOT BE POLLED
polls most storage devices for media insertion / removal and maintains
the list of devices exported. However, some hardware cannot be polled
for media changes without making noise or for other reasons. PC floppy
drives, Zip drives connected through an IDE interface and broken
optical drives falls into this category.
For such hardware
only exports the drive and rather than exporting volume as childs of
the drive, the
interface is exported on the drive itself.
supports this but it means that it is impossible to know ahead of time
what file system is on the media in the problematic drive, so in this
as the file system type and passes the mount options
as most media in such devices are formatted with either the
This also means that per-volume settings are
not possible; one can only specify settings per-drive.
was written by David Zeuthen <firstname.lastname@example.org>.