From owner-freebsd-stable Tue Feb 13 5:29:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fnord.ir.bbn.com (FNORD.IR.BBN.COM [192.1.100.210]) by hub.freebsd.org (Postfix) with SMTP id 6F38A37B65D for ; Tue, 13 Feb 2001 05:29:07 -0800 (PST) Received: (qmail 71772 invoked by uid 10853); 13 Feb 2001 13:29:06 -0000 To: Warner Losh Cc: Matt Dillon , John Reynolds , freebsd-stable@FreeBSD.ORG Subject: Re: sshd in 4.2-STABLE References: <200102120843.f1C8hhM03375@earth.backplane.com> <1843641235.20010212104321@road.omskelecom.ru> <14983.29328.298241.606895@whale.home-net> <200102122124.f1CLONW31606@harmony.village.org> From: Greg Troxel Date: 13 Feb 2001 08:29:06 -0500 In-Reply-To: Warner Losh's message of "Mon, 12 Feb 2001 14:24:23 -0700" Message-ID: Lines: 35 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > In message <200102120843.f1C8hhM03375@earth.backplane.com> Matt Dillon writes: > : ... or maybe installworld should just check to see if /etc/pam.conf is > : the unmodified older version and overwrite it with /usr/src/etc/pam.conf > : by default, rather then create little gotchas for people trying to > : upgrade. Hmmmmmm. > This would violate POLA worse than having it break, I think. The Debian package system does something like this, and I found it very helpful for the brief time I ran a GNU/Linux system. IIRC, packages distinguished between regular files (that weren't expected to change) and configuration files. When upgrading to a new version of a package, the rule was that if a config file was unchanged (same md5) from the installed package, it was replaced by the new version. If changed, the user was asked to merge/cope. Also, config files were left on pkg_delete (well, dpkg --remove), unless one asked to have them removed. I realize we are talking about the base system, but the concept is the same. This could perhaps be done by having a db of md5 sums of files under /etc that were 'installed' from the source tree (installworld, from-scratch install, mergemaster, automatic upgrade), and have upgrade procedures replace files that match (and that therefore have not been modified). While realizing that the instructions which tell you to merge /etc are clear: To me, POLA says that if I install 3.3, don't muck with stuff, and upgrade to 4.2, then I should have 4.2 without having to think about stuff I never mucked with (it's fair enough to have to understand stuff I changed). Greg Troxel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message