On Sat, Aug 11 2001 at 14:49:32 +0100, Matthew Theobalds wrote:
> I've been trying to set up my NetBSD machine as an NFS server so that I 
> can NFS Mount stuff onto my OS X machine.
[...]

> /etc/exports
> /home/matthew/public_html       maproot=root:wheel      192.168.1.3 # 
> That's the IP of the OS X Machine.
Looks Ok. - If DNS is working you can put the hostname there.

> /etc/inetd.conf
> # All RPC services commented out and inetd restarted.
This is not neccessary, NFS doesn't need any RPC service started by inetd.

> `/etc/rc.d/nfsd start' doesn't work, 
Because you haven't enabled the nfs server in the system startup
configuration file (rc.conf, see below) I guess.

> I also ran `/usr/sbin/mountd', which doesn't seem to start the mount 
> daemon.
Well, you have to start the RPC portmapper (rpcbind) first, rpc applications
like mountd depend on it. Unless you start mountd with "-d" all error
messages go to syslog (check /var/log/messages for errors), that's why
mountd seems to die silenty.

> Doing `mount_nfs sonic:/home/matthew/public_html Mount' from my OS X 
> machine gives the following error:
> 
> 	NFS Portmap: RPC: Port mapper failure - RPC: Timed out
> 	NFS Portmap: RPC: Port mapper failure - RPC: Timed out
That means: No connection to an RPC portmapper on the remote host.

Actually:

All you have to do is to put
	nfs_server=YES
in your /etc/rc.conf wich makes sure that when the systems starts all
neccessary daemons are started in the correct order.

And if you use libwrap to restrict accesses to inetd and other services
(hosts.allow/hosts.deny), make sure rpcbind, mountd and nfsd are not denied
for the client host. (The default is to allow all hosts to every service).

> Furthermore, all of the guides on the web are geared towards GNU/Linux 
> systems which seem to have additional mysterious rpc daemons.
Well, that's GNU/Linux...

Hope this helps,
	Thilo.
-- 
Dies ist Thilos Unix Signature! Viel Spass damit.