On Aug 31, 2009, at 8:44 AM, Steve Dickson wrote:
On 08/30/2009 12:37 PM, Chuck Lever wrote:
Since mount.nfs looks at the vers= option to determine pmap
parameters when
negotiating, it throws EINVAL if "4" is specified, even if the kernel
supports vers=4 for "nfs" type file systems.
Teach mount.nfs to ignore vers=4 and just pass the options to the
kernel.
How will mount.nfs know that the kernel now supports the "vers=4"
option?
The same way it knows after we add any new text-based feature... The
option will be passed down, and if the kernel supports it, it will
work. If not, mount(2) will return EINVAL, and the mount.nfs command
will report the problem.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html