[PATCH] lost volume.mount_point when unmounting...
david at fubar.dk
Thu Oct 27 08:38:23 PDT 2005
On Thu, 2005-10-27 at 01:31 -0200, Jonatan Liljedahl wrote:
> > Why is this difficult? If you get the volume.is_mounted property
> > change the device is not away in this case. If you need the mount
> > point options use the key block.device instead to identify the volume.
> > Or is there an other problem?
> I need the mount point when the device is removed (when
> volume.is_mounted is changed to "false"). But at this time the
> mount_point is already reset to "" which means I can't tell my desktop
> environment (ROX) to remove the device from the panel. Maybe it's
> possible to patch rox to allow id tags to be attached to panel items so
> that they can be changed/removed by that id instead of their path, but
> that's probably a lot of work.
So I think that what you need to do here is to keep a data structure
associating the hal udi and the mount point, e.g.
Note also that these two properties are updated as a single transaction,
e.g. atomically... this means that the PropertyModified D-BUS signal
actually tells your process (the client) that they were changed at the
same time... libhal, IIRC, doesn't tell you this though...
However.. you should just keep the mount_point around. Wouldn't this
More information about the hal