Re: [Tracker] Tracker - mount device uuid is wrong

[Martyn Russell <martyn lanedo com>]

On 14/10/10 12:38, Alexandru Tataru wrote:
> Hello again,

Hi,

>    The situation is like this. When you mount some volume on your host
> tracker automatically assigns to it a uuid and other general info, like
> if optical or not, etc. My problem is that on my linux build after I
> mount a volume tracker says that it could not get the uuid of the new
> volume and has assigned it's own uuid based on the file path. I took a
> look at the source code and where the mount fails it says that this
> situation has never been found, meaning that tracker always finds the
> volume uuid. Apparently I stumbled upon this situation and I want to
> know if you can tell me in what situations tracker ca not get the
> correct uuid for a mounted volume. Because I want the uuid to be always
> the same and not generated using the volume mounting path.

Historically, we used to use HAL for the unique identifier and it was 
always guaranteed. Since we don't use HAL directly, we use GIO's 
GVolumeMonitor the unique ID is not guaranteed for all devices.

We know using the path is a flaw but at the time it was considered a 
safe enough alternative (at least for cases like MeeGo). We don't 
actually have any more information to go on. We could a hash of the 
label, but then that can change OR be the same as another device so 
that's not useful either. We can't use the capacity or size because that 
too varies.

If you have an idea about how we could improve this, we are open to 
suggestions.

--
Regards,
Martyn