From owner-freebsd-current Fri Feb 12 17:02:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05379 for freebsd-current-outgoing; Fri, 12 Feb 1999 17:02:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05352 for ; Fri, 12 Feb 1999 17:02:17 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id QAA28339; Fri, 12 Feb 1999 16:56:48 -0800 (PST) Date: Fri, 12 Feb 1999 16:56:48 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Jay Nelson cc: current@FreeBSD.ORG Subject: Re: Heads up! /etc/rc.conf.site is dead. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mergemaster is your friend. On Fri, 12 Feb 1999, Jay Nelson wrote: > I may have missed this earlier in the thread, but has anyone given any > consideration to upgrade installs? If an upgrade doesn't plant the new > default files in /etc/default[s] after an upgrade, we now have two > places and twice the files to compare on upgrade. > > As unorthodox as it sounds, if these defaults are meant to be > unchanged, wouldn't a place like /boot/rc, or something similar, make > sense? Upgrades get the new whistles, and administrators can fiddle > files in /etc to their heart's content. > > -- Jay > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message