On Mar 19, 2009, at Mar 19, 2009, 7:13 AM, Steve Dickson wrote:
Steve Dickson wrote:
Chuck Lever wrote:
Our defaults should be settings that work well out of the box in
most environments.
If that isn't the case yet for NFSv4, then we shouldn't make it
the default.
Believe me.. with all the push back I'm getting from both the
client and
server side... I being to think the Linux community simply does not
want
move forward... but unfortunately I can accept that as option...
which
the the reason I will continue to push for changes that will move
us forward...
This comment was uncalled for and I hope it does not imped on the
productive
dialogue we were having...
I should have made it clear that I don't have any problem with having
NFSv4 as the default. My interest is that our NFSv4 implementation is
ready for our users when it becomes the default, and our development
team has a reasonably good understanding of what the problems will
be. When NFSv4 becomes the default, I want it to be a step forward.
I currently don't see the benefit a mount config file would add for an
NFSv4 transition. It's something we will have to live with for a long
while, so I think we should take the time and effort to get it right.
--
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
