From owner-freebsd-hackers  Sat Aug 23 11:30:19 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA08391
          for hackers-outgoing; Sat, 23 Aug 1997 11:30:19 -0700 (PDT)
Received: from actcom.co.il (baum@actcom.co.il [192.114.47.1])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA08369
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 23 Aug 1997 11:30:12 -0700 (PDT)
Received: from localhost by actcom.co.il  with SMTP
	(8.8.6/actcom-0.2) id VAA11630;
	Sat, 23 Aug 1997 21:22:27 +0300 (EET DST)
	 (rfc931-sender: baum@localhost)
Date: Sat, 23 Aug 1997 21:22:26 +0300 (EET DST)
From: Alexander Indenbaum <baum@actcom.co.il>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: A Joseph Koshy <koshy@india.hp.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: Checking the integrity of system files 
In-Reply-To: <9558.872358868@time.cdrom.com>
Message-ID: <Pine.SUN.3.96-heb-2.07.970823212014.5099B-100000@actcom.co.il>
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, Jordan K. Hubbard wrote:

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

Are you considering to move to RPM-like package management? 

  Alexander Indenbaum
  baum@actcom.co.il