From owner-freebsd-arch Thu Dec 20 8:44: 4 2001 Delivered-To: freebsd-arch@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 68E1A37B419; Thu, 20 Dec 2001 08:44:00 -0800 (PST) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 16H6KN-0000oe-00; Thu, 20 Dec 2001 18:45:51 +0200 From: Sheldon Hearn To: Robert Watson Cc: "Alexander N. Kabaev" , freebsd-arch@FreeBSD.ORG Subject: Re: Why special handling of nfsclient kernel support in etc/rc? In-reply-to: Your message of "Thu, 20 Dec 2001 11:40:51 EST." Date: Thu, 20 Dec 2001 18:45:51 +0200 Message-ID: <3139.1008866751@axl.seasidesoftware.co.za> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 20 Dec 2001 11:40:51 EST, Robert Watson wrote: > We need a better general solution for sysctls relating to this, I suspect. Actually, I don't think Alexander's assertion that the manual loading of NFS client support in rc supports sysctl manipulation. Looking at the scripts, sysctl stuff is done in rc.network, but only if the nfs sysctl node exists. It tries to do its own module loading there as well. So I still need an answer back from Doug about this, although your point is valid. I just don't want a discussion on a generalized solution for dynamically loaded sysctls to hijack my question. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message