From owner-freebsd-arch Thu Dec 20 7: 7:34 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 B3C8F37B405; Thu, 20 Dec 2001 07:07:27 -0800 (PST) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 16H4ov-00009x-00; Thu, 20 Dec 2001 17:09:17 +0200 From: Sheldon Hearn To: dougb@FreeBSD.org Cc: freebsd-arch@FreeBSD.org Subject: Why special handling of nfsclient kernel support in etc/rc? Date: Thu, 20 Dec 2001 17:09:17 +0200 Message-ID: <616.1008860957@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 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); } I ask because I'd like to reintroduce my original "late mounting of remote filesystems" support before 4.5-RELEASE (with the release engineer's permission, of course). I noticed that my patch no longer applies because of the quoted change, but I can't see why the quoted change is necessary. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message