On Mon, 9 May 2011 02:53:30 Anders Johansson wrote:
On Sunday 08 May 2011 18:06:27 j debert wrote:
the children?" tactic used by politicians. It doesn't seem to occur to them that new users may more likely be put off than experienced users by the resource greedy and untimely behaviour of these disk indexers.
Except that it only happens once, at the very beginning. Once everything has been indexed, it only looks at new activity, one file at a time.
Didn't work that way on my system. Once it was installed (and I have *no* idea how it got there) the laptop was never the same.
The people complaining about it have never let it run once to completion (which doesn't really take that long or cause that much trouble), so they have never seen the use
Anders
Now you're generalising. You have no idea what I (or anyone else who has complained about it) have done and seen, because you weren't here watching over my shoulder. Disk indexers should be built into the FS, should run in the background, only ever wake up when the CPU is idle and get the hell out of the way when another process asks for CPU cycles. The user should never know that they're there, until they want to search for something. So far, I've never yet seen one work that way on Linux. That might be the programmers' intention, but the reality is far different. Until someone can make one work properly, they're just an exercise in frustration for the user who wants to simply get the job done. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org