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

[Dag-Erling Smørgrav]

Rick Macklem <rmacklem at uoguelph.ca> writes:
> 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.)

I don't understand why you would want to do that.  Can't you just change
"oldnfs" back to "nfs" in the old stack?

Hmm, it occurred to me that there is currently no way to tell the kernel
that two drivers conflict with eachother.  Perhaps I should take a shot
at implementing a DRIVER_CONFLICT macro to mirror DRIVER_DEPEND.

BTW, don't take this personally, I'm very grateful for (and impressed
with) your NFS work, other than this little nit :)

DES
-- 
Dag-Erling Smørgrav - des at des.no