From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <bc6f8e4df70d9aa2f92981fb0e238eb6@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] nfsserver problems
From: "Russ Cox" <rsc@plan9.bell-labs.com>
In-Reply-To: <7e4737ea4b.micken@privat.utfors.se>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Mon, 28 Apr 2003 11:16:16 -0400
Topicbox-Message-UUID: 99b11774-eacb-11e9-9e20-41e7f4b1d025

By default, kfs does not allow connections from ``none''
unless someone else has already authenticated on the
connection.  Nfsserver connects as none (NFS has no
real authentication, so there's not much choice here)
on a fresh connection, hence the authentication fails.

You can run

	disk/kfscmd noneattach

to allow none to attach on fresh connections, but you'll
still only be none.  I use this to start an NFS server on my
local VMware network, so that my Linux VM can mount
files from Plan 9.

	#!/bin/rc

	rfork n
	slay nfsserver|rc
	slay portmapper|rc
	9fs boot
	rm -f /srv/nfs
	srvfs nfs /n/boot
	aux/portmapper
	aux/nfsserver -Cc /lib/ndb/nfs -f /srv/nfs

Russ