On Monday May 29, chip@valinux.com wrote:
> According to Matthias Andree:
> > Merging the v2 fixes for 2.2.16-pre and deferring v3 for 2.2.17-pre
> > would be the better way to go, then, would not it, in the meanwhile,
> > util-linux could be fixed.
>
> Perhaps ... *IF* they can be separated cleanly. Trond? Neil?
They probably can be separated cleanly. Just remove everything inside
#if CONFIG_NFSD_V3 / #endif
etc.
However I really don't see the point.
The old tools should work just as well as they ever did.
For nfs-client you wont be able to mount using V3 without a new "mount"
program, but you couldn't before. Nothing is lost.
For nfs-server, there should be no problem exporting NFSv3 as the
user-level tools already had some form of support.
There are elements of functionality that aren't available without
using the new tools, but in every case, the default is the old
behaviour.
In short, I can see no reason why the "new" kernel code would not work
with the "old" user level code at least as well (and in some cases
better than) the "old" kernel code worked with the old tools.
If that is not the case, then the "new" kernel code needs to be
fixed. Are there any known failure scenarios?
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:23 EST