From owner-freebsd-current Tue Feb 9 18:44:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23779 for freebsd-current-outgoing; Tue, 9 Feb 1999 18:44:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23748 for ; Tue, 9 Feb 1999 18:43:55 -0800 (PST) (envelope-from rkw@nomad.dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.8.8/8.8.8) with ESMTP id UAA00922; Tue, 9 Feb 1999 20:42:40 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Tue, 9 Feb 1999 20:42:40 -0600 (CST) From: Richard Wackerbarth To: Sheldon Hearn cc: John Fieber , jack , Matthew Dillon , current@FreeBSD.ORG Subject: Re: Heads up! /etc/rc.conf.site is dead. In-Reply-To: <92091.918611109@axl.noc.iafrica.com> 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 But, I would not expect/allow "defaults" to be the mechanism which includes the "real" values. Perhaps this should be pushed into the script that will source both. On Wed, 10 Feb 1999, Sheldon Hearn wrote: > > The only difference is the addition of a "no touchees" reference copy > > in /etc/defaults that gets sourced before rc.conf so any essential > > variables introduced in an upgrade will have a safety fallaback in > > case you don't properly upgrade your rc.conf. > > That's it? That's what all this is about? Hell, now that you've put it > like that, it sounds like a really _great_ idea. Even the choice of > directory name ``defaults'' makes sense, now. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message