Date: Fri, 4 Mar 2005 10:56:50 +0100 From: Philip Paeps <philip@FreeBSD.org> To: Mike Silbersack <silby@silby.com> Cc: cvs-src@FreeBSD.org Subject: Re: cvs commit: src/share/examples/etc make.conf Message-ID: <20050304095650.GF36450@fasolt.home.paeps.cx> In-Reply-To: <20050303134339.N811@odysseus.silby.com> References: <200503020349.j223n2t8025709@repoman.freebsd.org> <20050302181242.GA64751@hellblazer.celabo.org> <20050303134339.N811@odysseus.silby.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-03-03 13:45:13 (-0600), Mike Silbersack <silby@silby.com> wrote: > On Wed, 2 Mar 2005, Jacques A. Vidrine wrote: > > On Wed, Mar 02, 2005 at 03:49:02AM +0000, Tom Rhodes wrote: > > > trhodes 2005-03-02 03:49:02 UTC > > > > > > Add NO_RCMDS to the list. > > > > Cool, now just change the default to NO_RCMDS=true (^_^) > > With the current state of things, wouldn't that just ensure that users would > end up having older and more stale versions of the R-commands sitting around > on their drives? It seems like the security scripts should notify people of > old binaries sitting around in /bin and other related paths... Perhaps we could modify mergemaster to do a find -mtime +1 or something to that effect? If we can assume that mergemaster is run sometime 'soon' after an installworld? After installing a new world, I usually go around manually through most of my base system looking for stale files and killing them. I don't think mergemaster -- or anything else, for that matter -- should go around blindly nuking files older than a certain age under / and /usr, but it would be nice if it could warn users of their existence. As an alternative to mtime, we could compare the checksums of the files under /usr/obj with the installed versions and warn of differences? - Philip -- Philip Paeps Please don't Cc me, I am philip@freebsd.org subscribed to the list. Liquidity tends to run out.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050304095650.GF36450>