From owner-freebsd-arch Thu Dec 20 12:16:39 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id E984037B416 for ; Thu, 20 Dec 2001 12:16:27 -0800 (PST) Received: (qmail 22275 invoked from network); 20 Dec 2001 20:16:27 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Dec 2001 20:16:27 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <616.1008860957@axl.seasidesoftware.co.za> Date: Thu, 20 Dec 2001 12:16:09 -0800 (PST) From: John Baldwin To: Sheldon Hearn Subject: RE: Why special handling of nfsclient kernel support in etc/rc? Cc: freebsd-arch@FreeBSD.org, dougb@FreeBSD.org 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 20-Dec-01 Sheldon Hearn wrote: > > Hi Doug, > > I refer to the following change you made to src/etc/rc: > > revision 1.286 > date: 2001/10/19 06:50:52; author: dougb; state: Exp; lines: +19 -4 > Handle the lack of nfs server or client support in the kernel by > kldload'ing the appropriate modules before enabling the service. > > Why is this needed? Shouldn't the vfsload() code in mount_nfs(1) handle > this? > > error = getvfsbyname("nfs", &vfc); > if (error && vfsisloadable("nfs")) { > if(vfsload("nfs")) > err(EX_OSERR, "vfsload(nfs)"); > endvfsent(); /* clear cache */ > error = getvfsbyname("nfs", &vfc); > } There's no nfs.ko. mount_nfs should be updated to load 'nfsclient' instead. If this happens, then arguably, the nfs_client_enable variable in rc.conf should just go away and not be used. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message