From owner-freebsd-arch Mon Sep 18 15: 9:42 2000 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 233E637B424; Mon, 18 Sep 2000 15:09:39 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA92173; Mon, 18 Sep 2000 16:09:34 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA33920; Mon, 18 Sep 2000 16:09:22 -0600 (MDT) Message-Id: <200009182209.QAA33920@harmony.village.org> To: Kris Kennaway Subject: Re: sysctl on boot. Cc: arch@FreeBSD.org, sjr@home.net In-reply-to: Your message of "Mon, 18 Sep 2000 14:50:42 PDT." References: Date: Mon, 18 Sep 2000 16:09:22 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message