On 19/11/12 13:29, Myklebust, Trond wrote: > Note that the mount command should in any case not be relying on rpcbind > to decide whether or not the server supports NFSv4. Of course.... > > As for minor version negotiation, RFC3530 already tells you how to do > this: the client has to start with the highest version that it supports, > and then walk that number down until the server stops replying with > NFS4ERR_MINOR_VERS_MISMATCH. Perfect... I think we should do *all* v4 negotiation from the mount command... It's so much acceptable to replace mount.nfs binaries than kernels... > > Note that if you want to do this in userland before calling the mount > syscall, then the spec does allow you to "ping" the NFSv4 server with an > empty COMPOUND. The type of functionality will allow us to better deal with legacy servers, IMHO.. 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
