All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: nfs@lists.sourceforge.net
Subject: Status of NFS over IPv6
Date: Fri, 29 Jun 2007 14:37:47 +0200	[thread overview]
Message-ID: <20070629123747.GA1034@uio.no> (raw)

Hi,

What's the current status of NFS over IPv6 in Linux? There are HOWTOs out
there, but most patches seem to be against old kernel versions, and
completely unable to run both client and server from the same kernel tree.
Additionally, I see mentions of replacements for portmap, but no clear
upstream URL or updated versions anywhere. Also, there seems to be a separate
git tree maintained by Chuck Lever, but gitweb hides any special patches it
might have in tons of upstream patches.

I'd very much like to be able to sew all of this together at some point,
but it's very hard to get a decent overview of it all. Does anyone have a
"current status" or "plans for the near feature" summary?

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

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-06-29 12:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29 12:37 Steinar H. Gunderson [this message]
2007-06-29 22:01 ` Status of NFS over IPv6 Chuck Lever
2007-06-29 22:27   ` Steinar H. Gunderson
2007-07-02  9:36   ` Aurélien Charbon
2007-07-02 11:33     ` [NFS] " Le Rouzic
2007-07-02 16:23       ` Chuck Lever
2007-07-23 12:26         ` Le Rouzic
2007-07-26  7:43           ` Prasad P

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=20070629123747.GA1034@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 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.