From: Steve Dickson <SteveD@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: libtirpc and nis
Date: Wed, 03 Jun 2009 11:14:44 -0400 [thread overview]
Message-ID: <4A269364.2080304@RedHat.com> (raw)
In-Reply-To: <200906031002.38551.vapier@gentoo.org>
Mike Frysinger wrote:
> the libtirpc package is self described as a "standalone package". i wonder
> how far that actually goes. wrt NIS, it requires the system C library to
> provide NIS functionality or you get a build failure in a few files. would be
> nice if libtirpc were usable without any NIS baggage at all.
NIS used RPC procedures to communicate. As it stands today
NIS is currently using the RPC procedures glibc. In the
future there is a very good chance that NIS will start
using the RPC procedures in libtirpc especially if
IPV6 support is needed...
So I'm a bit confused on what you mean by "NIS baggage"
in the libtirpc package.
steved.
next prev parent reply other threads:[~2009-06-03 15:17 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 [this message]
[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
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=4A269364.2080304@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--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 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.