From owner-freebsd-arch Fri Dec 21 6:45:26 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1E2A537B416; Fri, 21 Dec 2001 06:45:23 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id BAA09323; Sat, 22 Dec 2001 01:45:20 +1100 Date: Sat, 22 Dec 2001 01:45:23 +1100 (EST) From: Bruce Evans X-X-Sender: To: John Baldwin Cc: Sheldon Hearn , , Subject: RE: Why special handling of nfsclient kernel support in etc/rc? In-Reply-To: Message-ID: <20011222013124.S4898-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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, John Baldwin wrote: > On 20-Dec-01 Sheldon Hearn wrote: > > 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. The above code (and similar code in N other mount utilities) has been undead for more than 3 years now. vfs modules should be automatically loaded by mount(2) if the above code doesn't do it first. Presumably mount(2) also fails to load nfs due to similar naming problems. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message