From owner-freebsd-hackers Sat Aug 23 12:39:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA10715 for hackers-outgoing; Sat, 23 Aug 1997 12:39:14 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA10710 for ; Sat, 23 Aug 1997 12:39:10 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x2LzK-0004nj-00; Sat, 23 Aug 1997 12:36:46 -0700 Date: Sat, 23 Aug 1997 12:36:46 -0700 (PDT) From: Tom Samplonius To: A Joseph Koshy cc: freebsd-hackers@freebsd.org Subject: Re: Checking the integrity of system files In-Reply-To: <199708230908.CAA05685@palrel1.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 23 Aug 1997, A Joseph Koshy wrote: > > Hi, > > -current being what it supposed to be, I find that as time passes my > system as getting filled up with the carcasses of old and abandoned > programs. At the minimum this can be a space wasting nuisance, and > may also leave way for security breaching > > Is there any way, barring parsing the output of `make install' to > or `make release' to determine the list of `current' files on a system? > > I'm looking at a registry of files maintaining sizes, permissions, checksums > of files, against which I can check a system. > > If such a registry is to be added, what is a good place to add it? > > (a) add the functionality to `install' (but this won't handle ports stuff) > (b) a separate program callable at install or release time or port addition > time. > > Koshy > > mtree can do some of this. See the manpage. Tom