From owner-freebsd-current Wed Feb 10 05:29:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25599 for freebsd-current-outgoing; Wed, 10 Feb 1999 05:29:01 -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 FAA25594 for ; Wed, 10 Feb 1999 05:29:00 -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 HAA01535; Wed, 10 Feb 1999 07:28:42 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Wed, 10 Feb 1999 07:28:42 -0600 (CST) From: Richard Wackerbarth To: John Fieber cc: jack , 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 On Wed, 10 Feb 1999, John Fieber wrote: > On Wed, 10 Feb 1999, jack wrote: > > > If /etc/rc.conf only contains changes from the defaults when > > man something_or_other tells the user to find and edit > > something_or_other_flags in /etc/rc.conf the entry won't be > > there to edit. > > Why must it contain only changes? Is there any reason it > couldn't be a copy of the default rc.conf on a new installation? Alternately, it could be a copy of the default file with every item commented out. That would provide the clues for those who need to edit values and still not mess up the default behavior of a new install with old options that might have changed but were not explicitly overridden. The documentation in the file could also suggest that the user remove anything that they do not need. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message