Linux NFS development
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: nfs@lists.sourceforge.net
Subject: Re: need info on IPv6 support for NFS in RHEL and SLES	distros
Date: Wed, 29 Aug 2007 23:08:28 +0200	[thread overview]
Message-ID: <20070829210828.GA21877@uio.no> (raw)
In-Reply-To: <46D59C8F.8070508@oracle.com>

On Wed, Aug 29, 2007 at 12:19:27PM -0400, Chuck Lever wrote:
> No Linux distribution contains IPv6 support for NFS right now.  The 
> implementation is still being developed.

Speaking of which, what's missing now? I see text-based mounts, client-side
IPv6 RPC and server-side transport switch (of which the first two are already
in mainline, and the last seems to be on its way) -- my impression was that
these are all important building blocks. I guess nfs-utils will also need
some patching, and an IPv6 transport will be needed for plugging into the
server side transport switch, but after that?

/* Steinar */
-- 
Homepage: http://www.sesse.net/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-08-29 21:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3DFE68BCB5D6994994AA6CB1EC581EA30411E61E@qcaexc02.asiapacific.cpqcorp.net>
2007-08-29 14:33 ` need info on IPv6 support for NFS in RHEL and SLES distros Trond Myklebust
2007-08-29 16:19 ` Chuck Lever
2007-08-29 21:08   ` Steinar H. Gunderson [this message]
2007-08-29 21:16     ` Chuck Lever
2007-08-29 21:18     ` Trond Myklebust

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=20070829210828.GA21877@uio.no \
    --to=sgunderson@bigfoot.com \
    --cc=nfs@lists.sourceforge.net \
    /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