nfsserver, portmapper, pcnfsd – NFS service|
aux/nfsserver [ rpc–options... ] [ nfs–options... ]|
aux/pcnfsd [ rpc–options... ]
aux/portmapper [ rpc–options... ]
These programs collectively provide NFS access to Plan 9 file
servers. Nfsserver, pcnfsd, and portmapper run on a Plan 9 CPU
server, and should be started in that order. All users on client
machines have the access privileges of the Plan 9 user none. Currently
only NFS version 2 is served. |
The rpc–options are all intended for debugging:
The nfs–options are:
–t Listen for incoming TCP calls, rather than UDP calls.
NFS clients must be in the Plan 9 /lib/ndb database. The machine name is deduced from the IP address via ndb/query. The machine name specified in the NFS Unix credentials is completely ignored.
Pcnfsd is a toy program that authorizes PC–NFS clients. All clients
are mapped to uid=1, gid=1 (daemon on most systems) regardless
of name or password.
A simple /lib/ndb/nfs might contain: |
A typical entry in /rc/bin/cpurc might be:
aux/nfsserver –a tcp!pie –a tcp!yoshimi –c /lib/ndb/nfs
Assuming the CPU server's name is eduardo, the mount commands on the client would be:
/etc/mount –o soft,intr eduardo:pie /n/pie
Note that a single instance of nfsserver may provide access to
several 9P servers.
/lib/ndb/nfs List of uid/gid maps.|
/sys/log/nfs Log file.
It would be nice to provide authentication for users, but Unix
systems provide too low a level of security to be trusted in a
Plan 9 world.|
RFC1057, RPC: Remote Procedure Call Protocol Specification, Version 2, describes Sun's RPC protocol.
RFC1094, NFS: Network File System Protocol Specification, describes NFS version 2.
RFC1813, NFS Version 3 Protocol Specification.
RFC3530, Network File System (NFS) version 4 Protocol.