All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <ooo@electrozaur.com>
To: Anna Schumaker <Anna.Schumaker@netapp.com>,
	Benjamin Coddington <bcodding@redhat.com>,
	Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: mount default minor version behavior
Date: Tue, 11 Nov 2014 18:27:05 +0200	[thread overview]
Message-ID: <546238D9.2030804@electrozaur.com> (raw)
In-Reply-To: <54622ADF.4080807@Netapp.com>

On 11/11/2014 05:27 PM, Anna Schumaker wrote:

> 
> I don't think so. Right now users know that if they don't use a minor
> version then they'll be getting a v4.0 mount. I think we should keep
> this behavior so we don't accidentally break people's configuration.
> 

This would be inconsistent and there for unexpected.

What you suggest is:
* if user specifies no version then start with 4.1, work down to supported version
* if user specifies major=4 only try 4.0
* if user specifies major.minor only try major.minor

I think a more expect behavior would be:
* if user specifies no version then start with 4.1, work down to supported version
* if user specifies major=4 start with 4.1 til 4.0
* if user specifies major.minor only try major.minor

The preferred (implicit) minor is 1 in all cases

The question is did users of major=4 meant 4.0 and were lazy to type ".0"
or did they mean "don't try 3 or 2"

Current system compatibility is already changing by moving all
case 1 above from 4.0 to 4.1 by the next yum update. I think it would
be reasonable to also change case 2. And have a consistent semantics.

> Anna
> 

Thanks
Boaz


  reply	other threads:[~2014-11-11 16:27 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 14:39 mount default minor version behavior Benjamin Coddington
2014-11-11 15:01 ` Weston Andros Adamson
2014-11-11 15:15   ` Benjamin Coddington
2014-11-11 15:01 ` Trond Myklebust
2014-11-11 15:20   ` Benjamin Coddington
2014-11-11 15:24     ` Trond Myklebust
2014-11-11 15:27     ` Anna Schumaker
2014-11-11 16:27       ` Boaz Harrosh [this message]
2014-11-11 19:19         ` Frank Filz
2014-11-11 19:25         ` Steve Dickson
2014-11-11 19:16   ` Steve Dickson
2014-11-11 20:43     ` Trond Myklebust
2014-11-12 13:08       ` Steve Dickson
2014-11-12 14:31         ` Trond Myklebust
2014-11-12 15:10           ` Steve Dickson
2014-11-12 15:28             ` Trond Myklebust
2014-11-12 15:37               ` Chuck Lever
2014-11-12 18:10                 ` Steve Dickson
2014-11-12 18:41                   ` Trond Myklebust
2014-11-12 20:07                     ` J. Bruce Fields
2014-11-12 20:30                       ` Steve Dickson
2014-11-12 20:17                     ` Anna Schumaker
2014-11-12 20:32                       ` Steve Dickson
2014-11-12 22:42                         ` Trond Myklebust
2014-11-13 17:57                           ` Steve Dickson
2014-11-13 18:52                             ` Trond Myklebust
2014-11-13 19:02                               ` J. Bruce Fields
2014-11-13 19:26                                 ` Trond Myklebust
2014-11-13 19:55                                   ` J. Bruce Fields
2014-11-13 20:22                                     ` Trond Myklebust
2014-11-13 20:38                                       ` J. Bruce Fields
2014-11-13 15:07                   ` Chuck Lever
2014-11-13 20:31                     ` Steve Dickson
2014-11-12 17:27               ` Steve Dickson
2014-11-11 16:38 ` Chuck Lever
2014-11-17 19:47   ` Benjamin Coddington
2014-11-17 21:02     ` Chuck Lever
2014-11-12 13:09 ` Benjamin Coddington
2014-11-12 14:36   ` Trond Myklebust
2014-11-12 15:01     ` Benjamin Coddington

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=546238D9.2030804@electrozaur.com \
    --to=ooo@electrozaur.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=bcodding@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.