From owner-freebsd-current Wed Sep 19 5:25:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id B260E37B414; Wed, 19 Sep 2001 05:25:43 -0700 (PDT) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id OAA25960; Wed, 19 Sep 2001 14:25:42 +0200 (MET DST) Date: Wed, 19 Sep 2001 14:25:42 +0200 (CEST) From: Harti Brandt To: Cc: Subject: mount_nfs problem... Message-ID: <20010919142034.S31209-100000@beagle.fokus.gmd.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Peter, after your Mega-commit mounting of NFS file systems does not work if NFS is not compiled into the kernel. The problem is in the following code snippet in sbin/mount_nfs: error = getvfsbyname("nfs", &vfc); if (error && vfsisloadable("nfs")) { if(vfsload("nfs")) err(EX_OSERR, "vfsload(nfs)"); endvfsent(); /* clear cache */ error = getvfsbyname("nfs", &vfc); } The *vfs* functions seem to rely on the fact that the module is named exactly like the file system. vfsload() does not load the named file system type, but the named kernel module. Now the kernel module for the client code is named 'nfsclient' so a change of the above to if(vfsload("nfsclient")) appears to work (but looks rather misleading to the casual reader - what kind of file system is 'nfsclient'?) harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fhg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message