Re: nfs vs nfsserver

[Paul Goyette <paul%whooppee.com@localhost>]

On Mon, 22 Dec 2008, Andrew Doran wrote:

> > I was trying to build a port-amd64 kernel which is an NFS server.  (It
> > is also an NFS client, but I intend to load the kernel nfs module for
> > that.)
>
> That's not a supported configuration at this time because the NFS build
> process is too complicated. As a module nfsserver requires nfs. For static
> builds you should be able to either component in isolation but that is only
> to preserve the existing behaviour. The two mutually exclusive paths are:
>
> - one or both built into the kernel
> - nfs or nfs+nfsserver as modules

Ah, kewl.  Thanks.  I'll load them both as modules.

> > So perhaps both references to the variable should simply be replaced by
> > the NFS_MAXUIDHASH macro, and eliminate the variable completely?
> >
> > Comments?  Other alternatives?
>
> Please don't eliminate the variable as it's a tuneable that can be patched
> in the field without a recompile. It could live in nfs_subs.c.

Hmmm.  Since the only two uses of the variable seem to limit the size of 
totally different lists, maybe they should have been two separate 
variables?  :)

I'll leave them alone.


----------------------------------------------------------------------
|   Paul Goyette   | PGP DSS Key fingerprint: |  E-mail addresses:   |
| Customer Service | FA29 0E3B 35AF E8AE 6651 |  paul%whooppee.com@localhost   |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette%juniper.net@localhost |
|                  |                          | pgoyette%netbsd.org@localhost  |
----------------------------------------------------------------------