[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A6DFFD.9030202@gmail.com>
Date: Wed, 25 Jul 2007 07:30:37 +0200
From: Rene Herman <rene.herman@...il.com>
To: david@...g.hm
CC: Nick Piggin <nickpiggin@...oo.com.au>,
Ray Lee <ray-lk@...rabbit.org>,
Jesper Juhl <jesper.juhl@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
ck list <ck@....kolivas.org>, Ingo Molnar <mingo@...e.hu>,
Paul Jackson <pj@....com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: -mm merge plans for 2.6.23
On 07/25/2007 07:12 AM, david@...g.hm wrote:
> On Wed, 25 Jul 2007, Rene Herman wrote:
>> It certainly doesn't run for me ever. Always kind of a "that's not the
>> point" comment but I just keep wondering whenever I see anyone
>> complain about updatedb why the _hell_ they are running it in the
>> first place. If anyone who never uses "locate" for anything simply
>> disable updatedb, the problem will for a large part be solved.
>>
>> This not just meant as a cheap comment; while I can think of a few
>> similar loads even on the desktop (scanning a browser cache, a media
>> player indexing a large amount of media files, ...) I've never heard
>> of problems _other_ than updatedb. So just junk that crap and be happy.
>
> but if you do use locate then the alturnative becomes sitting around and
> waiting for find to complete on a regular basis.
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?
Rene.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists