From owner-freebsd-arch Fri Dec 21 8:59:54 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 3170337B41A; Fri, 21 Dec 2001 08:59:29 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011221165929.PEFA20122.rwcrmhc53.attbi.com@peter3.wemm.org>; Fri, 21 Dec 2001 16:59:29 +0000 Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fBLGxSs82396; Fri, 21 Dec 2001 08:59:28 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9CC8238CC; Fri, 21 Dec 2001 08:59:28 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: John Baldwin Cc: Sheldon Hearn , freebsd-arch@FreeBSD.ORG, dougb@FreeBSD.ORG Subject: Re: Why special handling of nfsclient kernel support in etc/rc? In-Reply-To: Date: Fri, 21 Dec 2001 08:59:28 -0800 From: Peter Wemm Message-Id: <20011221165928.9CC8238CC@overcee.netplex.com.au> 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 John Baldwin wrote: > > 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. But "nfs" is exported via kldxref and should be loadable via "kldload nfs". Secondly, this is why I did not remove nfsiod to start with. I was planning to redo it as a wrapper that did the module load, and emulated the arguments by translating them into a sysctl to set the number of kernel nfsiod's and then exiting. This would solve the ordering problem entirely and wouldn't depend on actually having nfs file systems in fstab in order to set the sysctl's. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message