From owner-freebsd-arch Sun Sep 17 12: 4:36 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 1180037B422 for ; Sun, 17 Sep 2000 12:04:33 -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 NAA86878; Sun, 17 Sep 2000 13:04:29 -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 NAA24354; Sun, 17 Sep 2000 13:04:22 -0600 (MDT) Message-Id: <200009171904.NAA24354@harmony.village.org> To: arch@freebsd.org, sjr@home.net Subject: sysctl on boot. Date: Sun, 17 Sep 2000 13:04:22 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Roznowski reports in PR conf/19629 that there's a weakness in /etc/rc.sysctl. As it stands now, it runs early in the boot process. And it needs to run early in the boot process for many sysctls. However, there is a problem. If you modload a driver or module after this point, any variables set early in the boot process will not be effective (because the setting fails). 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. A long term fix might be to give the kernel a memory so it can initialize the sysctls from the get go. However, that's much harder to pull off and a whole lot more work. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message