From owner-freebsd-questions Tue Oct 16 16:45: 7 2001 Delivered-To: freebsd-questions@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [171.66.112.163]) by hub.freebsd.org (Postfix) with ESMTP id 4EF6637B40E; Tue, 16 Oct 2001 16:45:04 -0700 (PDT) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id QAA39213; Tue, 16 Oct 2001 16:43:19 -0700 (PDT) Date: Tue, 16 Oct 2001 16:43:19 -0700 (PDT) From: Annelise Anderson To: Christopher Smith Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: mergemaster -- whats the best way? In-Reply-To: <200110162320.JAA13142@yowie.cc.uq.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 17 Oct 2001, Christopher Smith wrote: > [chomp] > > > P'raps even merge both ideas into one - a "preprocessor" that does the file > comparisons to find files modified since install that then passes those > files in an exclusion list... > The problem with ignoring modified files is that you modify (for example) /etc/group when you add a user, but sometimes there's a new "system" group that needs to be added (for example, the network group was added a few years ago). Changes get made to /etc/defaults/rc.conf that require changes to /etc/rc.conf; also the /etc/.ssh stuff. So leaving modified files alone is not a complete solution. Annelise -- Annelise Anderson Author of: FreeBSD: An Open-Source Operating System for Your PC Available from: mall.daemonnews.org and amazon.com Book Website: http://www.bittreepress.com/FreeBSD/introbook/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message