From 2c1dc529e8d9b1ab2d8ccb8abb1efed836584616 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Thu, 9 Apr 2009 21:34:49 -0400 Subject: [PATCH] Add a note about handling non-hal backends --- gio/gvolume.c | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/gio/gvolume.c b/gio/gvolume.c index ef550d822..6e3f8b711 100644 --- a/gio/gvolume.c +++ b/gio/gvolume.c @@ -60,18 +60,24 @@ * is called, then it will be filled with any error information. * * - * It is sometimes necessary to directly access the underlying + * 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 predefind strings as names for the different kinds - * of identifiers: #G_VOLUME_IDENTIFIER_KIND_HAL_UDI, - * #G_VOLUME_IDENTIFIER_KIND_LABEL, etc. Use g_volume_get_identifier() + * of identifiers: #G_VOLUME_IDENTIFIER_KIND_HAL_UDI, + * #G_VOLUME_IDENTIFIER_KIND_LABEL, etc. Use g_volume_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_manger_find_device_string_match(). + */ static void g_volume_base_init (gpointer g_class); static void g_volume_class_init (gpointer g_class,