From owner-freebsd-hackers Sat Aug 23 20:11:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA01516 for hackers-outgoing; Sat, 23 Aug 1997 20:11:41 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA01511 for ; Sat, 23 Aug 1997 20:11:35 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id MAA00881; Sun, 24 Aug 1997 12:33:36 +0930 (CST) Message-Id: <199708240303.MAA00881@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Alexander Indenbaum cc: "Jordan K. Hubbard" , A Joseph Koshy , freebsd-hackers@freebsd.org Subject: Re: Checking the integrity of system files In-reply-to: Your message of "Sat, 23 Aug 1997 21:22:26 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 Aug 1997 12:33:34 +0930 From: Mike Smith 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? Not trivially, due to enthusiastic use of "install -C" > > 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. > > Are you considering to move to RPM-like package management? Can you be more specific than "RPM-like"? Yes in that there will be management tools, no in that they are unlikely to be the RPM tools. mike