All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@gmx.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Steve Dickson <SteveD@redhat.com>, Neil Brown <neilb@suse.de>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: nfs-utils and unfsd
Date: Tue, 5 Aug 2008 21:24:45 +0200	[thread overview]
Message-ID: <200808052124.45907.bernd-schubert@gmx.de> (raw)
In-Reply-To: <BFA7510D-B3C2-48FB-8C17-80008A362B6D@oracle.com>

On Tuesday 05 August 2008, Chuck Lever wrote:
> On Aug 5, 2008, at 2:13 PM, Steve Dickson wrote:
> > Chuck Lever wrote:
> >> There is a generic RPC server helper in nfs-utils called rpc_init().
> >> This API will need to be modified to support IPv6 in statd and
> >> mountd,
> >> at least.
> >>
> >> However, there is a comment inside support/nfs/rpcmisc.c, where
> >> rpc_init() resides, that suggests that this interface is also used by
> >> unfsd.
> >>
> >> Is it OK for me to modify nfs-utils' copy of this function, or is
> >> there
> >> any kind of ABI restriction between unfsd and nfs-utils?
> >
> > I don't see any problem... Is there even a supported/maintained
> > version
> > of unfsd out there today? I did a quick google search and didn't find
> > anything but man pages...
>
> I found this ancient web page:
>
> http://rpm.pbone.net/index.php3/stat/4/idpl/6572509/com/unfs3-0.9.20-1.el3.
>pp.i386.rpm.html
>
> which suggests there is no binary dependency between unfsd and nfs-
> utils.

This is unfs3, which is a rewritten from scratch by Pascal Schmidt and so 
unrelated to unfsd.

      reply	other threads:[~2008-08-05 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 19:55 nfs-utils and unfsd Chuck Lever
2008-08-04 20:18 ` Chuck Lever
2008-08-05 18:13 ` Steve Dickson
     [not found]   ` <48989831.2030808-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-08-05 18:30     ` Chuck Lever
2008-08-05 19:24       ` Bernd Schubert [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=200808052124.45907.bernd-schubert@gmx.de \
    --to=bernd-schubert@gmx.de \
    --cc=SteveD@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.