From owner-cvs-all Fri Aug 28 19:52:31 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02577 for cvs-all-outgoing; Fri, 28 Aug 1998 19:52:31 -0700 (PDT) (envelope-from owner-cvs-all) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02570 for ; Fri, 28 Aug 1998 19:52:26 -0700 (PDT) (envelope-from dillon@backplane.com) Received: (dillon@localhost) by apollo.backplane.com (8.8.8/8.6.5) id TAA21595; Fri, 28 Aug 1998 19:51:30 -0700 (PDT) Date: Fri, 28 Aug 1998 19:51:30 -0700 (PDT) From: Matthew Dillon Message-Id: <199808290251.TAA21595@apollo.backplane.com> To: Matthew Dillon Cc: "Jordan K. Hubbard" , Mike Smith , committers@FreeBSD.ORG Subject: Re: make.conf Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk : * In general, No auditing of rc.conf.local is necessary. No merging, : no editing, no nothing. In rare cases someone may turn on something : in rc.conf that we may want to turn off in rc.conf.local, but we : haven't come across such a case yet even when drastic changes are : being made to rc.conf by the committers. I should make a correction here... after the initial turning off of certain basic services turned on in rc.conf.local, that is. Once you've set up your base overrides in rc.conf.local, you generally don't have to mess with it during future upgrades even if the distribution rc.conf file goes through major changes. -Matt