Date: Wed, 17 Oct 2007 12:33:39 +0200 From: "Simon L. Nielsen" <simon@FreeBSD.org> To: Stefan Esser <se@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/locate/locate locate.rc updatedb.sh Message-ID: <20071017103338.GB1003@zaphod.nitro.dk> In-Reply-To: <200710170727.l9H7Rpk3028513@repoman.freebsd.org> References: <200710170727.l9H7Rpk3028513@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2007.10.17 07:27:51 +0000, Stefan Esser wrote: > se 2007-10-17 07:27:51 UTC > > FreeBSD src repository > > Modified files: > usr.bin/locate/locate locate.rc updatedb.sh > Log: > The previous version included too many file system types in the scan, > since "local" includes also synthetic file systems (e.g. /dev, /proc) > and loopback mounts. > > This version uses lsvfs to identify file system types that are local > and additionally not synthetik, loopback mounts, or read-only. This > has been suggested by Craig Rodrigues half a year ago. The patch that > has been committed is based on his suggestion, but slightly modified. Are you sure all read-only file systems should be excluded? I quite often have systems with some filesystem mounted read-only (often /), though granted most of those are "embedded" which doesn't run updatedb. Which kind of file systems were you thinking should be excluded by the RO part which isn't already removed by loopback|network|synthetic ? I'm not certain read-only shouldn't be excluded, but I just want to point out there are cases where read-only still might be a local and interesting file system. -- Simon L. Nielsen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071017103338.GB1003>