From owner-freebsd-current Thu Jan 8 16:04:19 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA21129 for current-outgoing; Thu, 8 Jan 1998 16:04:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA21021 for ; Thu, 8 Jan 1998 16:03:56 -0800 (PST) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (ppp101.wcc.net [208.6.232.101]) by wcc.wcc.net (8.8.7/8.8.7) with ESMTP id SAA06688; Thu, 8 Jan 1998 18:00:37 -0600 (CST) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.7) id SAA00410; Thu, 8 Jan 1998 18:03:47 -0600 (CST) (envelope-from joelh) Date: Thu, 8 Jan 1998 18:03:47 -0600 (CST) Message-Id: <199801090003.SAA00410@detlev.UUCP> To: freebsd-current@freebsd.org Subject: current w/ tripwire From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is anybody running -current with Tripwire? I ask because it would seem to me that it would be a pain to manually take down the system from all external access, verify the tripwire files, make world, make install, rebuild the tripwire files, and bring the system back up, every time you want to update. I was wondering if anybody has thought of a better scheme than this basic one. Best wishes, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped