The Volume interface represents user-visible objects that can be mounted.
Note, when porting from GnomeVFS, Volume is the moral equivalent of GnomeVFSDrive.
Mounting a Volume instance is an asynchronous operation. For more information about asynchronous
operations, see AsyncResult and Task. To
mount a Volume, first call mount with (at
least) the Volume instance, optionally a MountOperation
object and a TaskReadyCallback.
Typically, one will only want to pass null for the
MountOperation if automounting all volumes when a desktop session starts since it's not desirable to put up a lot of dialogs asking
for credentials.
The callback will be fired when the operation has resolved (either with success or failure), and a
AsyncResult instance will be passed to the callback. That callback should then call
mount.end with the Volume instance and the
AsyncResult data to see if the operation was completed successfully. If an
error is present when mount.end is called, then it will be filled
with any error information.
Volume Identifiers # {volume-identifier}
It is sometimes necessary to directly access the underlying operating system object behind a volume (e.g. for passing a volume to an
application via the commandline). For this purpose, GIO allows to obtain an 'identifier' for the volume. There can be different kinds of
identifiers, such as Hal UDIs, filesystem labels, traditional Unix devices (e.g. `/dev/sda2`), UUIDs. GIO uses predefined strings as names
for the different kinds of identifiers: g_volume_identifier_kind_uuid,
g_volume_identifier_kind_label, etc. Use get_identifier to
obtain an identifier for a volume.
Note that g_volume_identifier_kind_hal_udi will only be available when the gvfs hal volume monitor is
in use. Other volume monitors will generally be able to provide the g_volume_identifier_kind_unix_device
identifier, which can be used to obtain a hal device by means of libhal_manager_find_device_string_match.