This must have been answered before, but a quick googling did not reveal the answer. Why does clicking the "find file" button in konq result in intense and seemingly endless hard drive whirring, while the console command "locate ...." provides the answer almost before the <enter> key is pressed on the keyboard?
On Tuesday 26 September 2006 09:57, kanenas@hawaii.rr.com wrote:
This must have been answered before, but a quick googling did not reveal the answer. Why does clicking the "find file" button in konq result in intense and seemingly endless hard drive whirring, while the console command "locate ...." provides the answer almost before the <enter> key is pressed on the keyboard?
As much as I know, it's because konqueror really searches the files on disk, while locate just looks in it's database that is updated only every 24 hours (on my system). So locate wouldn't find any newly inserted files unless you run updatedb first. Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch
On 26 September 2006 08:57, kanenas@hawaii.rr.com wrote:
while the console command "locate ...." provides the answer almost before the <enter> key is pressed on the keyboard?
Sometime ago, I initiated a thread where I described that with the KDE version of SuSE 10.1 (3.5.1) couldn't open the the original sources of cdrtools ("http://freshmeat.net/projects/cdrecord/"), although they were open in SuSE 9.2. The specific problem was that Ark couldn't read the TAR files of the sources. After some messages, we discovered that: 1. The files could be open by the untar command line; 2. The author of cdrtools, Jörg Schilling, uses a different tool to tar is files; 3. KDE has a Ktar routine and the conclusion was that this was the source of the problem. I'm not into the KDE development, but I guess that exists a KLocate routine in the (exists a KLocate application "http://www.duffy1.franken.de/rjakob/") the is used instead of the command line equivalent. Regards Lívio
On 9/26/06, Lívio Cipriano
On 26 September 2006 08:57, kanenas@hawaii.rr.com wrote:
while the console command "locate ...." provides the answer almost before the <enter> key is pressed on the keyboard?
Sometime ago, I initiated a thread where I described that with the KDE version of SuSE 10.1 (3.5.1) couldn't open the the original sources of cdrtools ("http://freshmeat.net/projects/cdrecord/"), although they were open in SuSE 9.2. The specific problem was that Ark couldn't read the TAR files of the sources. After some messages, we discovered that:
1. The files could be open by the untar command line; 2. The author of cdrtools, Jörg Schilling, uses a different tool to tar is files; 3. KDE has a Ktar routine and the conclusion was that this was the source of the problem.
I'm not into the KDE development, but I guess that exists a KLocate routine in the (exists a KLocate application "http://www.duffy1.franken.de/rjakob/") the is used instead of the command line equivalent.
Regards
Lívio
Anybody has got an affection for Beagle?? --
Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (4)
-
Daniel Bauer -
Duff Mckagan -
kanenas＠hawaii.rr.com -
Lívio Cipriano