public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH][nfs-utils] configuration: Fix a typo in configure.ac
Date: Mon, 1 Mar 2010 09:22:07 -0500	[thread overview]
Message-ID: <20100301142207.GC17660@fieldses.org> (raw)
In-Reply-To: <4B8BCB7D.1030202-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>

On Mon, Mar 01, 2010 at 09:13:17AM -0500, Steve Dickson wrote:
> 
> 
> On 03/01/2010 08:55 AM, J. Bruce Fields wrote:
> > No, that's not enough.  They may be accessing the server through other
> > clients.
> Understood... just curious, would you happen to know of any clients
> that use 4.1 as the default? Was there any at this year's Connectathon?

I don't know what their policies are.

Someone will turn it on by default at some point, and we've no way to
ensure they'll do that at the same point that the linux 4.1 server is
up to spec.

> > We need users to make a conscious decision to turn on the server-side.
> > It's not enough to do it only on the client side.
> Right. At this point people will either have to recompile nfs-utils using
> the --enable-nfsv41 flag or edit their initscript and do the echo trick... 
> So isn't having to do one of the above be construed as conscious decision?

Recompiling with the --enable-nfsv41 flag isn't a good way for a *user*
to request 4.1 support.  It really only makes sense for *distributors*.

--b.

  parent reply	other threads:[~2010-03-01 14:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-20 23:45 [PATCH][nfs-utils] configuration: Fix a typo in configure.ac Trond Myklebust
     [not found] ` <1266709510.3507.1.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-02-22 18:22   ` J. Bruce Fields
2010-03-01 12:57     ` Steve Dickson
     [not found]       ` <4B8BB9B8.8040703-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-03-01 13:25         ` J. Bruce Fields
2010-03-01 13:48           ` Steve Dickson
     [not found]             ` <4B8BC5B9.1020304-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-03-01 13:55               ` J. Bruce Fields
2010-03-01 14:13                 ` Steve Dickson
     [not found]                   ` <4B8BCB7D.1030202-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-03-01 14:22                     ` J. Bruce Fields [this message]
2010-03-01 12:41   ` Steve Dickson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100301142207.GC17660@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=SteveD@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox