Skip to main content
Welcome guest. | Register | Login | Post

Graphical desktop search without indexing (based grep, find etc.)?

10 replies [Last post]
libervisco's picture
Offline
Joined: 2006-05-04

10th point of this interesting list mentions desktop search not dependent on indexing. Beagle and stuff like that need to update their database and so does the command line locate tool. I *hate* updatedb to be honest so I am actually interested in killing the need for it.

So, there are tools like grep and find which search the files directly. However using them might sometimes be tedious for certain searches. I'm wondering if there is a graphical tool which uses these kinds of tools (basically being their frontend) to do complete desktop search.

Searchmonkey seems close, but I'm wondering if there is something similar that actually has a simple beagle like (or google-like if you will) one-line-for-search interface. Smiling

tbuitenh's picture
Offline
Joined: 2005-12-21
Something like

Something like this?

#!/bin/bash

find ~ -name "*`xprompt`*" | xless

I don't have xprompt or xless installed, so this might need to be edited a bit.

Offline
Joined: 2006-03-28
I guess kfind works like

I guess kfind works like this too. Not sure though, but since I don't have anything that does any indexing (except for slocate, which I sometimes like to use; but this just is updated manually), I guess that's what it uses. It also finds stuff from directories that are not listed in slocate, so I think it uses find, grep and probably cat (to look for stuff inside the file).

libervisco's picture
Offline
Joined: 2006-05-04
tbuitenh wrote: Something
tbuitenh wrote:

Something like this? ...

Well that seems quite simple although I couldn't try it outright since xprompt is missing from repository and my attempt to run the binary I got from some 64bit RPM failed because it's looking for libxaw.so.8 which is missing from my system. Oddly enough I only have libxaw.so.7. Is this old little program actually looking for a newer version? Weird...

So that's what spoils it, in addition to the interface being slightly archaic overall...

reptiler wrote:

I guess kfind works like this too.

I'm just trying kfind. I am searching everything under "/" just to see how that goes.. As expected, it's taking its time. I'm not sure if it would take longer to just updatedb. Laughing out loud

But.. I suppose the benefit is in searching for stuff within specific directories rather than the whole disk.

Maybe best would be to just remove updatedb from cron and run it when you actually want to search for something, if updatedb is really faster in scanning everything than "find" is.

In any case kfind seems like a good answer to the original question.

Thank you

Offline
Joined: 2006-03-28
As you probably know there

As you probably know there are different implementations of locate. The default one is in the findutils. I actually like slocate, which doesn't show stuff the searching user cannot access, the original locate does this. My Fedora-notebook has, as far as I remember (might also be the Debian-server at work), mlocate, which does only index changes and therefor is quicker (except on the first run of course).
EasyLFS has slocate as an option, as replacement for locate, and it indexes the filesystem before it finished the installation so that on the first boot there is an initialized locate-db.

libervisco's picture
Offline
Joined: 2006-05-04
I've actually used mlocate

I've actually used mlocate when I was using Arch. It really is a lot faster and I wonder why don't more distros use it by default.

I think I'll replace slocate with it immediately.

Thanks

libervisco's picture
Offline
Joined: 2006-05-04
I just built and installed

I just built and installed mlocate and now I'm getting this when trying to run updatedb:

updatedb: can not open a temporary file for `/usr/local/var/mlocate/mlocate.db'

Apparently /usr/local/var/* doesn't exist at all so something tells me there is a wrong path somewhere.. it should probably be /var/mlocate/mlocate.db, but that doesn't exist either. Weird. :\

Offline
Joined: 2006-03-28
Did you compile it by

Did you compile it by yourself?
If so the parameter localstatedir should help you:

Quote:

--localstatedir=DIR modifiable single-machine data [PREFIX/var]

libervisco's picture
Offline
Joined: 2006-05-04
I doubt that would help. I

I doubt that would help. I just tried it and it didn't. If I don't specify a path there is a default path which apparently was /usr/local yet it didn't create a var there. Doesn't really make much sense...

Offline
Joined: 2006-03-28
I just compiled it, from a

I just compiled it, from a clean archive (maybe you try make distclean or at least make clean before retrying) and it seems to work okay.
./configure --prefix=/usr --localstatedir=/var

free-zombie's picture
Offline
Joined: 2006-03-08
isn't it in the archive ?

isn't it in the archive ? I'd better have a look at it and maybe package it then ;-)

on second though... hasn't anyone written a locate clone using inotify yet ?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.