Linux NFS development
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@redhat.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Jim Rees <rees@umich.edu>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NFSv4: Add modalias for "nfs4"
Date: Fri, 27 Apr 2012 11:41:33 -0400	[thread overview]
Message-ID: <20120427154123.GE13189@zod.bos.redhat.com> (raw)
In-Reply-To: <1335540074.3910.9.camel@lade.trondhjem.org>

On Fri, Apr 27, 2012 at 03:21:15PM +0000, Myklebust, Trond wrote:
> > > > OK.  So either this patch needs to go in, or something needs to add:
> > > > 
> > > > alias nfs4 nfs
> > > > 
> > > > to a conf file so modprobe picks it up.  I figured the kernel could add
> > > > the alias itself.  Is there a reason not to?
> > > 
> > > Yes. This is a legacy feature that we want to encourage people to move
> > > their systems off...
> > 
> > So essentially what needs to happen is:
> > 
> > - Recent distros still ship the modalias in a conf file
> > - Upstream nfs-utils starts translating 'mount -t nfs4' into 'mount -t
> >   nfs -overs=4' in /sbin/mount.nfs4
> > - Upstream releases that
> > - Distros drop the alias.
> > 
> > Right?
> 
> No. Really all we need to do is add a printf() to /sbin/mount.nfs4 to
> the effect that this is a legacy feature and that '-t nfs -overs=4' is
> the recommended mount option. Perhaps the distros can also have their
> distro upgrade utilities edit /etc/fstab to upgrade those automatically.
> 
> Then the distros can drop the alias whenever they think it is
> appropriate.

My limited experience shows that people won't change their habits until
those habits simply no longer work.  Adding a printf is probably a fine
thing to do, but I'm not sure it will have much impact on how people go
about mounting NFSv4 filesystems.  That leads me to believe that the
alias will be carried along for quite a while.

Anyway, the immediate problem can be solved by just keeping the alias in
a conf file.  If that's what is recommended for now, OK.

josh

  reply	other threads:[~2012-04-27 15:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 13:10 [PATCH] NFSv4: Add modalias for "nfs4" Josh Boyer
2012-04-27 13:30 ` Jeff Layton
2012-04-27 14:19 ` Jim Rees
2012-04-27 14:48   ` Josh Boyer
2012-04-27 14:50     ` Myklebust, Trond
2012-04-27 14:53       ` Josh Boyer
2012-04-27 15:02         ` Myklebust, Trond
2012-04-27 15:14           ` Josh Boyer
2012-04-27 15:21             ` Myklebust, Trond
2012-04-27 15:41               ` Josh Boyer [this message]
2012-04-27 15:27           ` Jeff Layton

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=20120427154123.GE13189@zod.bos.redhat.com \
    --to=jwboyer@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@umich.edu \
    /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