From owner-freebsd-arch Thu Dec 20 7:15:41 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 DBBE037B417 for ; Thu, 20 Dec 2001 07:15:38 -0800 (PST) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 16H4wm-0000Co-00; Thu, 20 Dec 2001 17:17:24 +0200 From: Sheldon Hearn To: "Alexander N. Kabaev" Cc: 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 10:10:25 EST." Date: Thu, 20 Dec 2001 17:17:24 +0200 Message-ID: <793.1008861444@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 10:10:25 EST, "Alexander N. Kabaev" wrote: > rc script tries to set sysctl variables which are only > available when NFS is present in the kernel. But not at the point where NFS filesystems are mounted. Why can't we rely on mount_nfs's calls to vfsload() to do the right thing for us? I propose that the checks for the presence of NFS support should accompany the calls to sysctl, not the calls to mount_nfs. Ciao, SHeldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message