From owner-freebsd-hackers  Sat Aug 23 11:01:03 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA07336
          for hackers-outgoing; Sat, 23 Aug 1997 11:01:03 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA07330
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 23 Aug 1997 11:00:57 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id KAA09562; Sat, 23 Aug 1997 10:54:28 -0700 (PDT)
To: A Joseph Koshy <koshy@india.hp.com>
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Checking the integrity of system files 
In-reply-to: Your message of "Sat, 23 Aug 1997 14:35:22 +0530."
             <199708230908.CAA05685@palrel1.hp.com> 
Date: Sat, 23 Aug 1997 10:54:28 -0700
Message-ID: <9558.872358868@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 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.

This is a problem which we're also trying to solve for distributions
(or a newer package format which replaced the old "split tarball"
distribution format) since you need the same information for upgrades.

My impression would be that we'd hack the install rules to also
"register" things installed through /usr/src.

					Jordan