From owner-freebsd-hackers Mon Apr 1 00:15:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA07957 for hackers-outgoing; Mon, 1 Apr 1996 00:15:31 -0800 (PST) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.RWTH-Aachen.DE [134.130.90.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07944 Mon, 1 Apr 1996 00:15:21 -0800 (PST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.6.12/8.6.9) id KAA21390; Mon, 1 Apr 1996 10:15:12 +0200 From: Thomas Gellekum Message-Id: <199604010815.KAA21390@ghpc6.ihf.rwth-aachen.de> Subject: Re: locate To: mpp@freefall.freebsd.org (Mike Pritchard) Date: Mon, 1 Apr 1996 10:15:10 +0200 (MET DST) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199604010600.WAA01868@freefall.freebsd.org> from Mike Pritchard at "Mar 31, 96 10:00:10 pm" Organization: Institut f. Hochfrequenztechnik, RWTH Aachen X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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. No, please. If the owner doesn't want to expose his files to the world, locate should respect this. > Another option is to keep two databases, one of all the public > files, as it does now. And a complete database that is > accessed with some new option on locate that would verify that > the file is accessible to the user before printing it out. I'd prefer a new option to locate which gives the name of (an) alternate database(s), so you could run locate for yourself. This could also be used to locate files on NFS-mounted filesystems. tg