From owner-freebsd-questions Thu Sep 23 3:50:50 1999 Delivered-To: freebsd-questions@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 319AE15662 for ; Thu, 23 Sep 1999 03:50:44 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11U6Qt-0001Ef-00; Thu, 23 Sep 1999 12:48:59 +0200 From: Sheldon Hearn To: Peter Duff Cc: freebsd-questions@FreeBSD.ORG Subject: Re: nfs exports In-reply-to: Your message of "Thu, 23 Sep 1999 18:02:17 +0800." <37E9FAA9.2C36400A@cs.curtin.edu.au> Date: Thu, 23 Sep 1999 12:48:59 +0200 Message-ID: <4752.938083739@axl.noc.iafrica.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999 18:02:17 +0800, Peter Duff wrote: > Sure Sheldon, I'm running it as root, and the filesystem is mounted. You forgot the output of the mount command. While you're at it, let's see the fstab. :-) The manpage for mount(2) says that a return of EPERM (which is what's causing the error message you see) means that the user is not super-user. However, the code indicate another possibility: Securelevel is greater than 1, but an nfs module needed to be loaded because NFS support wasn't in the kernel. It may also be that EPERM is returned on kernel module load failure, but I can't dig that deep into the kernel. :-) So if you still haven't gotten any more clueful advice from anyone else, all I can suggest (assuming the mount output and fstab that you send don't show anything) is that you compile NFS into the kernel instead of using a loadable module. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message