> You have to store them somewhere, and to place them on the indexed > volume seems natural to me. You should also set the "hidden" > attribute > in the Tracker attributes. In other cases, the preferred solution > would > be the data directory. > Another option would be to have them as an attribute of the root > directory, but that would only work with BFS volumes, of course. Until the attribute layer is usable everywhere ;-) > Of course, you might not want to have the index on the media, because > the space is limited. That might be true for a 4 GB USB stick, but > that's not really the case for a 1 TB external hard drive - I > wouldn't > want to clobber my system disk with its index data instead :-) A valid reason not to put the index on the volume is with multiuser, and read-only volumes (even though layers could work around this). One should still be able to index non user writable volumes this way... Another reason is to avoid conflicts with other users or different machines with different indexing settings, where each would overwrite the index each time to fit its own settings. > So I guess a better solution is needed here. But in any case, this is > a > mere technicality - it's nothing you should think about too much at > first, it can be easily refined/changed at a later time. It could also be made configurable. > I think this could be made an advanced setting, but when I, for > example, wanted to search some specs, I probably don't want only the > first 100KB of them indexed. Besides that, I don't think you usually > have so many large text documents on your disk unless you need them, > and then you probably want to have them indexed, anyway. We'll also want to not index stuff like .svn/* and others... or not as text at least. François.