Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Mike Frysinger <vapier@gentoo.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
	libtirpc <libtirpc-devel@lists.sourceforge.net>
Subject: Re: libtirpc and nis
Date: Thu, 04 Jun 2009 13:53:46 -0400	[thread overview]
Message-ID: <4A280A2A.2040007@RedHat.com> (raw)
In-Reply-To: <1244125476.5203.21.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>



Trond Myklebust wrote:
>>>>> libtirpc does not provide rpcsvc/nis.h
>>>> Hmm... I wonder what it would take to incorporate that file into
>>>> libitrpc... 
>>> rpcgen support. We already have the nis.x file in glibc's copy of the
>>> rpcsvc directory.
>> I'm thinking more of licensing issues..
> 
> I know. I'm saying that we're already distributing it through glibc. We
> don't need to distribute it again in libtirpc; we can just make use of
> the existing .x file.
Understood... But the ultimate goal here is to completely wean ourself
from the any of the glibc RPC code... so having similar header files
in a couple places is the price we are going to have to pay... IMHO...

steved.


  parent reply	other threads:[~2009-06-04 17:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 14:02 libtirpc and nis Mike Frysinger
2009-06-03 15:14 ` Steve Dickson
     [not found]   ` <4A269364.2080304-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-06-03 22:44     ` Mike Frysinger
2009-06-03 23:59       ` Chuck Lever
2009-06-04  0:12         ` Mike Frysinger
2009-06-04 10:03           ` Steve Dickson
     [not found]             ` <4A279C05.9030108-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-06-04 12:06               ` Trond Myklebust
     [not found]                 ` <1244117219.5203.12.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-04 14:15                   ` Steve Dickson
     [not found]                     ` <4A27D6FF.9070702-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-06-04 14:24                       ` Trond Myklebust
     [not found]                         ` <1244125476.5203.21.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-04 17:53                           ` Steve Dickson [this message]
2009-06-04 14:26               ` Chuck Lever
2009-06-04 14:28               ` Chuck Lever
2009-06-04 15:17                 ` Trond Myklebust
     [not found]                   ` <1244128639.5203.44.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-06-04 17:44                     ` Chuck Lever

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=4A280A2A.2040007@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=libtirpc-devel@lists.sourceforge.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=vapier@gentoo.org \
    /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