Date: Sat, 22 Dec 2001 01:45:23 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: John Baldwin <jhb@FreeBSD.ORG> Cc: Sheldon Hearn <sheldonh@starjuice.net>, <freebsd-arch@FreeBSD.ORG>, <dougb@FreeBSD.ORG> Subject: RE: Why special handling of nfsclient kernel support in etc/rc? Message-ID: <20011222013124.S4898-100000@gamplex.bde.org> In-Reply-To: <XFMail.011220121609.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011222013124.S4898-100000>