But wait:  Portmap runs on a server to supply port numbers to clients.
So why should portmap be required on an nfs client machine?  I've been running
an nfs client machine without portmap for several days, and I haven't noticed
any problems.

On Fri, Nov 19, 1999 at 02:35:05PM +0100, Hubert Feyrer wrote:
> On Fri, 19 Nov 1999, David Brownlee wrote:
> > > I'd like to set portmap=yes in the start-nfs block, but the problem is
> > > that portmap is started before that. Should we bother checking if either
> > > of portmap, nfs_client or nfs_server is set, to turn portmap on?
> > > 
> > 	That sounds reasonable to me.
> 
> So:
> 
> diff -u -r1.136 rc
> --- rc  1999/11/15 20:04:50     1.136
> +++ rc  1999/11/19 13:33:21
> @@ -262,7 +262,7 @@
>  echo -n 'starting rpc daemons:'
>  
>  # note that portmap is generally required for all other rpc services.
> -if checkyesno portmap; then
> +if checkyesno portmap || checkyesno nfs_client || checkyesno nfs_server;
> then
>         echo -n ' portmap';             portmap $portmap_flags
>  fi
> 
> Are there other services that would need to be added here?
> ypbind, ypserv, yppasswdd?
> 
> 
>  - Hubert
> 
> -- 
> NetBSD - Better for your uptime than Viagra