svn commit: r221124 - in head: . sbin/mount sbin/mount_nfs sys/amd64/conf sys/fs/nfsclient sys/i386/conf sys/ia64/conf sys/nfsclient sys/pc98/conf sys/powerpc/conf sys/sparc64/conf sys/sun4v/conf

[Rick Macklem]

> Rick Macklem <rmacklem at uoguelph.ca> writes:
> > "Dag-Erling Smørgrav" <des at des.no> writes:
> > > Ideally, both the old and the new NFS stack would use the same
> > > fstypes and sysctl names, but I don't know if there's any way we
> > > can
> > > prevent someone from compiling both into the kernel at the same
> > > time, or loading both modules.
> > If the scripts in /etc/rc.d are fixed to use the correct sysctl
> > naming,
> > do you think it matters which one is "vfs.nfs."?
> 
> Yes. There is a whole world outside the base system: munin, webmin,
> nagios etc. Are you going to change all of them as well?
> 
Well, another way it could be handled would be to put the sysctls and
the global variables they manipulate in a module shared by both clients,
like sys/nfs/nfs_lock.c (module "nfslock"). Then the same sysctl would
affect both clients. (I hesitate to create "yet another" module just
to share the sysctls, but since "nfslock" is used by both clients, it
should work ok, I think.)

What do you think of that?

If anyone else reading this has an idea/opinion, please let us know.

rick