Re: [Tracker] Prevent removed files from being removed from the db
- From: Nikolaus Rath <Nikolaus rath org>
- To: tracker-list gnome org
- Subject: Re: [Tracker] Prevent removed files from being removed from the db
- Date: Mon, 17 May 2010 15:12:32 -0400
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
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.
Best,
-Nikolaus
--
ÂTime flies like an arrow, fruit flies like a Banana.Â
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]