Re: [Tracker] Prevent removed files from being removed from the db



On Mon, 2010-05-17 at 15:12 -0400, Nikolaus Rath wrote:
Philip Van Hoof <spam-+mS4aLmNmLKG5XvV6lv2jw public gmane org> writes:
How can Tracker (reliably) detect if a resource is on an external drive?
I can't believe that this works for anything but the trivial case where
/dev/sdX is directly mounted. But if the disk is e.g. LUKS encrypted,
then there's already a device mapper in between. It get's even worse
with all the possibilities that FUSE and bind mounts offer.

HAL (or devicekit) has a unique ID for each removable device. We detect
and use this unique ID for this purpose.

If you can't believe this, why don't you try it?

Because don't feel familiar enough with tracker to confirm that the data
has really vanished (in contrast to me not being able to find it, see my
other mail about problems with searching for a simple test file). 

But I don't think there is any need for a demonstration. How can HAL (or

If you don't want to demonstrate the problem, then I'm afraid that we
don't want to help you.

devicekit, or any other program) possibly know if an arbitrary FUSE file
system stores its data on a removable device, the network, or just
copies it from /dev/urandom?

To put it differently, if I ask tracker to index /home/bla, and
/home/bla/mnt is a mount point with file system type 'fuse.fusexmp', how
are you going to determine if this is removable or not? I don't think
there is an API for that.

We don't consider FUSE mountpoints to be removable devices. I already
explained what we consider to be a removable device. Martyn also replied
to you that info.


Cheers,

Philip

-- 


Philip Van Hoof
freelance software developer
Codeminded BVBA - http://codeminded.be




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]