All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs@lists.sourceforge.net,  wildfire@progsoc.uts.edu.au
Subject: Re: NFS mount version?
Date: 14 Aug 2003 23:31:33 -0700	[thread overview]
Message-ID: <shssmo34eka.fsf@charged.uio.no> (raw)
In-Reply-To: <16188.12287.809594.752856@gargle.gargle.HOWL>

>>>>> " " == Neil Brown <neilb@cse.unsw.edu.au> writes:

     > On Wednesday August 13, wildfire@progsoc.uts.edu.au wrote:
    >> Hi all,
    >>
    >> Documentation/Changes in 2.6.0-test3 suggests the minimum
    >> version of nfs-utils to use is 1.0.5 yet even with 1.0.5 I
    >> still get messages like:
    >>
    >> Aug 13 18:09:35 clam kernel: nfs warning: mount version older
    >> than kernel
    >>
    >> Which version should I be using?

     > Some appropriate version of util-linux (I think).

Actually, support for NFS_MOUNT_VERSION 5 has not yet been merged into
any version of util-linux.

Note, though, that the only new feature added is support for
RPCSEC_GSS under NFSv2 and NFSv3. Unless you have some burning desire
to test krb5 authentication, you can ignore the above warning.

Cheers,
  Trond


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2003-08-15  6:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13  9:53 NFS mount version? Anand Kumria
2003-08-15  0:57 ` Neil Brown
2003-08-15  6:31   ` Trond Myklebust [this message]

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=shssmo34eka.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    --cc=wildfire@progsoc.uts.edu.au \
    /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.