Newbie Question

["Frank D. Engel, Jr." <fde101@fjrhome.net>]

Hi,

I am hoping someone can help me with this.

I am trying as an experiment to set up a small plan9 cluster as a set of 
computers in a VMWare environment.

I am using the latest 9front distribution, and currently have two VMs 
booting plan9 with one network adapter each, on a private network (not 
connected to the internet or to the host computer), with no DHCP being 
provided by VMWare, and am attempting manual isolated configuration for now.


As far as I can tell, I was able to get an auth server running, booting 
off its own installation, with authentication enabled on its 
filesystem.  It comes up without the window system running (as a cpu 
server) and "keyfs" is among the processes which are listed when I run 
"ps"; I was able to use auth/changeuser to create user accounts for the 
hostowner users "glenda" (for my file server) and another account for my 
auth server, and was able to arrange for secstored to start with the 
system (from cpurc) and that seems to be working - I also created 
accounts in there to match the two I created with auth/changeuser, and 
both accounts are defined on the filesystem. If I do "ps | grep listen" 
I see five processes running: two owned by the host owner and three by 
"none".

I have a second system set up which I intend to be the file server (more 
storage space) and I can successfully use "rcpu" to access the auth 
server from that one.  The file server is still booting as a terminal 
rather than a cpu server, and I created matching user accounts (newuser) 
on the filesystem on the file server.


The last part of the /lib/ndb/local file on the file server looks like this:


auth=fingers authdom=9cluster


ipnet=9cluster ip=192.168.81.0 ipmask=255.255.255.0

     fs=cabinet

     tftpd=cabinet

     auth=fingers

     authdom=9cluster

     dnsdomain=9cluster


# file server

sys=cabinet ether=005056301268 ip=192.168.81.10

     dom=cabinet.9cluster


# auth server

sys=fingers ether=00505635c452 ip=192.168.81.12

     dom=fingers.9cluster



As I understand it, the next step would be to enable authentication on 
the file server.  I do this by rebooting, adding -c to the bootargs and 
at the "config:" prompt entering "noauth" twice, then "end".


When I try to do this, I am getting this set of messages:


mount: auth_proxy: auth_proxy read fd: authread: auth protocol not finished

mount: mount /root: authread: auth protocol not finished


followed by a list of partitions then a new prompt for bootargs


I am interpreting this to mean that I missed something in my 
authentication configuration, but after trying several things, I am a 
bit lost on how to proceed with this.


Can someone point me in the direction of what I might be missing?


Thank you!