From owner-freebsd-hackers Sat Aug 23 02:08:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA00683 for hackers-outgoing; Sat, 23 Aug 1997 02:08:18 -0700 (PDT) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.235]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA00678 for ; Sat, 23 Aug 1997 02:08:12 -0700 (PDT) Received: from postbox.india.hp.com (postbox.india.hp.com [15.10.45.1]) by palrel1.hp.com (8.8.6/8.8.5) with ESMTP id CAA05685 for ; Sat, 23 Aug 1997 02:08:05 -0700 (PDT) Message-Id: <199708230908.CAA05685@palrel1.hp.com> Received: from localhost by postbox.india.hp.com with ESMTP (1.39.111.2/16.2) id AA120867122; Sat, 23 Aug 1997 14:35:22 +0530 To: freebsd-hackers@freebsd.org Subject: Checking the integrity of system files Date: Sat, 23 Aug 1997 14:35:22 +0530 From: A Joseph Koshy Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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