[PATCH] lost volume.mount_point when unmounting...

Jonatan Liljedahl lijon at kymatica.com
Wed Oct 26 20:31:36 PDT 2005

On Wed, 26 Oct 2005 21:29:47 +0200
Danny Kukawka <danny.kukawka at web.de> wrote:

> On Thursday 27 October 2005 00:57, Jonatan Liljedahl wrote:
> > HAL sets volume.mount_point to "" BEFORE volume.is_mounted is set to
> > "false".
> >
> > This makes it very difficult (impossible) for volume managers to
> > remove a device from the desktop if they are configured to react on
> > volume.is_mounted property change.
> 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.

> Btw. I think the patch break the the HAL specifications and the
> behavior of the key/property. If you not set back the mountpoint to
> empty if the device is not in /proc/mounts it would be possible to
> have old values in this key.

Does this matter? You can allways check with volume.is_mounted if it's
actually mounted...?

Could another way be to FIRST set volume.is_mounted to false and let
this event be sent and then reset mount_point after that, so when Ivman
triggers on is_mounted it is still there? Or would this mean some ugly
hack to sleep a while before resetting the mount_point?

/Jonatan    -=( http://kymatica.com )=-

More information about the hal mailing list