From owner-freebsd-hackers  Mon Apr  1 05:15:24 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA24682
          for hackers-outgoing; Mon, 1 Apr 1996 05:15:24 -0800 (PST)
Received: from whyy.org (jehrenkrantz@internal-gw.whyy.org [199.234.236.254])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA24677
          Mon, 1 Apr 1996 05:15:21 -0800 (PST)
Received: (from jehrenkrantz@localhost) by whyy.org (8.6.12/8.6.9) id IAA03816; Mon, 1 Apr 1996 08:16:42 -0500
Date: Mon, 1 Apr 1996 08:16:42 -0500 (EST)
From: Jeff Ehrenkrantz <jehrenkrantz@whyy.org>
To: Mike Pritchard <mpp@freefall.freebsd.org>
cc: freebsd-hackers@freefall.freebsd.org
Subject: Re: locate
In-Reply-To: <199604010600.WAA01868@freefall.freebsd.org>
Message-ID: <Pine.BSD/.3.91.960401081019.29803A-100000@whyy.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I also think that there is use for a switch with Locate allowing an 
expended db.
My only concern it that the expanded db doesn't become a security problem.
..je


On Sun, 31 Mar 1996, Mike Pritchard wrote:

> What do people think of the idea of changing locate & its database
> update script to keep a list of ALL files on the system, and
> not just those that can been seen by the world.  It always drives
> me nuts when I use locate to find something I *KNOW* is on
> my system, but it would not print it because it is in some directory
> that is mode 750, and not 755, but it is still accessable by
> my current uid/gid.
> ...............................