From owner-freebsd-arch Mon Sep 18 17:35: 3 2000 Delivered-To: freebsd-arch@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 05A2D37B422; Mon, 18 Sep 2000 17:35:01 -0700 (PDT) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA10903; Mon, 18 Sep 2000 17:34:55 -0700 (PDT) (envelope-from DougB@gorean.org) Date: Mon, 18 Sep 2000 17:34:55 -0700 (PDT) From: Doug Barton X-Sender: doug@dt051n37.san.rr.com To: Warner Losh Cc: Kris Kennaway , arch@FreeBSD.ORG, sjr@home.net Subject: Re: sysctl on boot. In-Reply-To: <200009182209.QAA33920@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Sep 2000, Warner Losh wrote: > In message Kris Kennaway writes: > : On Sun, 17 Sep 2000, Warner Losh wrote: > : > : > A short term fix is to just rerun /etc/rc.sysctl at the end of the > : > boot sequence, just before the secrelevel change. Stephen's PR > : > suggests this with a patch. I think it is good, but wanted to get > : > some feedback from others before doing this. > : > : rc.sysctl_early and rc.sysctl_late? > > I worry about a gratuitous change to the name. However, I could > easily see rc.sysctl have an early file and a late one settable by > rc.conf If I can speak from the "average user" standpoint, this scheme is fraught with disaster. In the long run it will be much easier to fix the sysctl's that can't be set twice than it would be to try and get users to figure out which ones are "early" and which ones are "late." This also accomplishes the task of making things work the way they should in the first place. :) Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message