From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 21 Apr 1998 12:59:21 +0200
From: Lucio de Re lucio@proxima.alt.za
Subject: [9fans] nfsserver
Topicbox-Message-UUID: 768c7b60-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19980421105921.5J3TTG2bI8-WF3l6xdS1OqPL609xBqzooMCifnpwA60@z>

According to arisawa@plan9.aichi-u.ac.jp :
> 
> ar> /etc/mount -o soft,intr plan9:9fs /n/9fs
> mount: plan9:9fs on /n/9fs: Stale NFS file handle
> mount: giving up on:
>    /n/9fs
> 
OK, time to ask the experts for some additional information.

1. The Stale NFS file handle is produced by nfsserver, based on a 
missing machine name in the client credentials.  Is this a Unix bug?
Three different releases of NetBSD produce the same result, user 0 and 
user 301 both producing 0@ and 301@ as the credentials.  The result is 
an empty client ID which cannot be matched in the configuration file
(should it be matched?).

2. NetBSD 1.2.1 and 1.3 both assume NFS version 3 and do not try a 
version 2 possibility.  Does the portmapper have the ability to trigger 
the demotion, or do I need to report to the NetBSD group that they 
should activate such demotion in their mount_nfs code?  Requesting 
version 2 services produces the desired result, give or take the Stale 
NFS file handle problem.

Forsyth?
-- 
Lucio de Re (lucio@proxima.alt.za)
Disclaimer: I'm working at getting my opinions to agree with me.