From owner-freebsd-stable Sat Apr 20 19:58:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from 12-234-22-238.client.attbi.com (12-234-90-219.client.attbi.com [12.234.90.219]) by hub.freebsd.org (Postfix) with ESMTP id 5B6FF37B417 for ; Sat, 20 Apr 2002 19:58:45 -0700 (PDT) Received: from Master.gorean.org (master.gorean.org [10.0.0.2]) by 12-234-22-238.client.attbi.com (8.12.2/8.12.2) with ESMTP id g3L2wiHt070213; Sat, 20 Apr 2002 19:58:44 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from Master.gorean.org (zoot [127.0.0.1]) by Master.gorean.org (8.12.2/8.12.2) with ESMTP id g3L2wkLr016278; Sat, 20 Apr 2002 19:58:46 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from localhost (doug@localhost) by Master.gorean.org (8.12.2/8.12.2/Submit) with ESMTP id g3L2wkAl016275; Sat, 20 Apr 2002 19:58:46 -0700 (PDT) X-Authentication-Warning: Master.gorean.org: doug owned process doing -bs Date: Sat, 20 Apr 2002 19:58:46 -0700 (PDT) From: Doug Barton X-X-Sender: doug@master.gorean.org To: D J Hawkey Jr Cc: freebsd-stable Subject: Re: /etc/defaults/rc.conf theory In-Reply-To: <20020420203338.A49337@sheol.localdomain> Message-ID: <20020420193955.O15997-100000@master.gorean.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 20 Apr 2002, D J Hawkey Jr wrote: > Um, you mean "after a new install", then? Would I therefore be correct in > inferring that what's is in place from a 4.5-REL[-pN] install (specifically, > /etc/rc.conf [en|dis]abling whatever is in /etc/defaults/rc.conf) will > actually result in the same runtime after an upgrade to 4.6-REL? No, actually. You can be reasonably certain that that things you've set explicitly will still function the same way. However, numerous factors can contribute to differences. Some examples off the top of my head: 1. Someone could comment out all the entries in inetd.conf, like was done on August 4th, 2001. 2. Someone could add new functions/new knobs which changes long-standing behavior of existing systems, like what's been done with the recent sendmail changes. 3. Someone could change dependency mapping, like has been done with portmap, and other services. > Worded differently, I certainly don't recall anyone saying /etc/rc.conf > should be an edited-down copy of /etc/defaults/rc.conf that guarantees > what is up and down; not until yesterday, anyway. Part of the problem has been disagreement as to how this file should be used. I decided to throw caution to the wind. :) > What I've seen has always stated that what's in /etc/rc.conf overrides > what's in /etc/defaults/rc.conf; by changing the latter, you certainly > may change someone's actual runtime, and that's one of (the last of, > now) the things that bothers me. You've blown POLA out of the water, and > without blatant warning or notification at the right time, that someone > is gonna get hurt. Exactly. Over time, there has been a general agreement that using defaults/rc.conf to change things out from under the user is a bad idea. This is part of my eagerness for mfc'ing things at this stage of the game... -current is going to be a pretty big shock for the unprepared. However, this "general agreement" has not always been adhered to. Thus, my advice to set the variables for the things you care about. > Have I missed a reassurance somewhere? No, I think that you're looking for a reassurance that doesn't exist. -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message