From owner-freebsd-current Fri Feb 12 17:00:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05175 for freebsd-current-outgoing; Fri, 12 Feb 1999 17:00:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tok.qiv.com (tok.qiv.com [205.238.142.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05170 for ; Fri, 12 Feb 1999 17:00:37 -0800 (PST) (envelope-from jdn@acp.qiv.com) Received: (from uucp@localhost) by tok.qiv.com (8.9.3/8.9.3) with UUCP id TAA16023 for current@FreeBSD.ORG; Fri, 12 Feb 1999 19:00:35 -0600 (CST) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.8/8.8.8) with SMTP id SAA00938 for ; Fri, 12 Feb 1999 18:40:50 -0600 (CST) (envelope-from jdn@acp.qiv.com) Date: Fri, 12 Feb 1999 18:40:50 -0600 (CST) From: Jay Nelson To: current@FreeBSD.ORG Subject: Re: Heads up! /etc/rc.conf.site is dead. In-Reply-To: <199902112056.UAA04933@keep.lan.Awfulhak.org> 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 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