On 07/25/2007 09:14 AM, [email protected] wrote:
On Wed, 25 Jul 2007 07:30:37 +0200, Rene Herman said:
Yes, but what's locate's usage scenario? I've never, ever wanted to use
it. When do you know the name of something but not where it's located,
other than situations which "which" wouldn't cover and after just
having installed/unpacked something meaning locate doesn't know about
it yet either?
My favorite use - with 5 Fedora kernels and as many -mm kernels on my
laptop, doing a 'locate moby' finds all the moby.c and moby.o and moby.ko
for the various releases.
Supposing you know the path in one tree, you know the path in all of them,
right? :-?
You want hard numbers? Here you go - 'locate' versus 'find'
These are ofcourse not necesary. If you discount the time updatedb itself
takes it's utterly obvious that _if_ you use it, it's going to be wildly
faster than find.
Regardless, I'll stand by "[by disabling updatedb] the problem will for a
large part be solved" as I expect approximately 94.372 percent of Linux
desktop users couldn't care less about locate.
Rene.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
