<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <blockquote cite="mid4408EA7F.7090601@sun.com" type="cite"> <blockquote type="cite"> <blockquote type="cite">like "info.scan_state" property, with values 'in_progress' and 'done'. </blockquote> </blockquote> </blockquote> This would be indeed a great solution to our problem. <blockquote cite="mid4408EA7F.7090601@sun.com" type="cite"> <blockquote type="cite">If so, it would be also possible to have a callback, like libhal_rescan_complete(). The ideal solution would be something like libhal_device_scan_complete(), but ... </blockquote> You're thinking in terms of libhal again... Libhal is just a wrapper. If there is such a property, you simply subscribe to "PropertyModified" signal, whatever D-BUS binding or wrapper library you're using. <blockquote type="cite"> <blockquote type="cite">free to scan or not scan for volumes whenever it feels like, or depending on runtime conditions known only to HAL. </blockquote> Can you explain to me the last two lines? I mean, why would it be a problem to eg invoke a signal to a user (ie through LibHal) after the probing/searching for volumes has finished? </blockquote> We could add a signal for that, but we could instead add a property and use the existing "PropertyModified" signal. Less code change that way. <blockquote type="cite">I noticed that in hald/blockdev.c </blockquote> hald/linux2/blockdev.c, actually., which is critical: I'm not talking about Linux-specific implementation, I'm talking about HAL in general. <blockquote type="cite">I guess this is what you mean. After that, blockdev_callouts_add_done() is called and the device is removed from the TDL and added to the GDL. </blockquote> That's what happens in the Linux backend. In general, device is added to GDL after all pre-probe (info.callouts.preprobe), probe and add (info.callouts.add) callouts are finished. <blockquote type="cite">So when a volume is added, that's a separate hotplug event? </blockquote> Depends on HAL implementation, but it doesn't matter ("hotplug events" in the Linux backend are not really what they sound like). What matters is that when a volume is added, that's a separate HAL device object and a separate "DeviceAdded" signal. -Artem. _______________________________________________ hal mailing list <a class="moz-txt-link-abbreviated" href="mailto:hal@lists.freedesktop.org">hal@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/hal">http://lists.freedesktop.org/mailman/listinfo/hal</a> </blockquote> </body> </html>