60
60
* is called, then it will be filled with any error information.
62
62
* <para id="volume-identifier">
63
* It is sometimes necessary to directly access the underlying
63
* It is sometimes necessary to directly access the underlying
64
64
* operating system object behind a volume (e.g. for passing a volume
65
65
* to an application via the commandline). For this purpose, GIO
66
66
* allows to obtain an 'identifier' for the volume. There can be
67
67
* different kinds of identifiers, such as Hal UDIs, filesystem labels,
68
68
* traditional Unix devices (e.g. <filename>/dev/sda2</filename>),
69
69
* uuids. GIO uses predefind strings as names for the different kinds
70
* of identifiers: #G_VOLUME_IDENTIFIER_KIND_HAL_UDI,
71
* #G_VOLUME_IDENTIFIER_KIND_LABEL, etc. Use g_volume_get_identifier()
70
* of identifiers: #G_VOLUME_IDENTIFIER_KIND_HAL_UDI,
71
* #G_VOLUME_IDENTIFIER_KIND_LABEL, etc. Use g_volume_get_identifier()
72
72
* to obtain an identifier for a volume.
75
* Note that #G_VOLUME_IDENTIFIER_KIND_HAL_UDI will only be available
76
* when the gvfs hal volume monitor is in use. Other volume monitors
77
* will generally be able to provide the #G_VOLUME_IDENTIFIER_KIND_UNIX_DEVICE
78
* identifier, which can be used to obtain a hal device by means of
79
* libhal_manger_find_device_string_match().
76
82
static void g_volume_base_init (gpointer g_class);
77
83
static void g_volume_class_init (gpointer g_class,
added
removed
gio/gvolume.c
