Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: nfs vs nfsserver


On Sun, Dec 21, 2008 at 06:13:10AM -0800, Paul Goyette 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

> 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.


Home | Main Index | Thread Index | Old Index