On 08/27/2009 01:58 PM, Chuck Lever wrote: > > On Aug 27, 2009, at 1:48 PM, Trond Myklebust wrote: > >> On Thu, 2009-08-27 at 10:14 -0400, Steve Dickson wrote: >>> I say we go with the proposed patch since its simple, architecturally >>> sound, will not cause problems down the road as long as nfs4 remains >>> a standalone file system and its done! Plus I have a patch waiting >>> in the wings that actually does make v4 the first mount that is >>> tried... making v4 the default version... >> >> I do worry that if, at some point, we do get rid of the nfs4 filesystem >> alias then we may find ourselves in trouble if we have a large base of >> mount programs out there that translate '-t nfs -overs=4' into '-t >> nfs4'. Well at that point, if that every and happens and if the mount command is the only thing that has to change it would a minor miracle... IMHO... >> >> I think that if you want to go down this path, you should somehow ensure >> that the resulting program is capable of passing '-t nfs -overs=4' down >> to the kernel (perhaps a configuration file option?). > > My impression was that this mount command behavior would be controlled > with a kernel version switch in mount.nfs, much the same way that we > already handle switching between text-based and legacy mounting. That > won't help with old nfs-utils on new kernels, though. Right... and I really don't want to adding yet another configuration option for something that should be so simple... steved. -- 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
