On Thu, Sep 26, 2013 at 11:35:46AM -0700, Wendy Cheng wrote: > On Thu, Sep 26, 2013 at 10:47 AM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > > > (BTW, out of curiosity: what kind of client is this that only supports > > NFSv2 and NFSv3? Even for an embedded system that's a bit surprising.) > > > > There are few floating around - at least I'm working on one at this moment. > > Look to me the upgrade issue is with user space packages (e.g. where > "mount" lives). Embedded systems can take their user space packages > from certain "distribution"s that are not necessarily sync well with > individual linux upstream tool distribution, even the kernel itself is > reasonably updated. > > And don't shoot a messenger :) .. I'm just describing the practices I > have been observed. OK. I'm not sure what standard to hold this sort of change to. I'm inclined to use the same "it's OK if and only if nobody notices" standard as for normal kernel interfaces. Which means we've already got enough evidence to put off dropping NFSv2 support for a few more years, at least on the server side.... --b. -- 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
