Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] Switching from glibc RPC to TI RPC
Date: Wed, 20 Mar 2013 10:27:35 +0000	[thread overview]
Message-ID: <1586733.G7AaCq5rbs@helios> (raw)
In-Reply-To: <1363772243-370-1-git-send-email-marcin.juszkiewicz@linaro.org>

On Wednesday 20 March 2013 10:37:17 Marcin Juszkiewicz wrote:
> rpcbind needed removal of yellow pages support (whatever it is).

Isn't that NIS? Will that affect the ypbind-mt / yp-tools recipes recently 
added back into meta-networking?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  parent reply	other threads:[~2013-03-20 10:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20  9:37 [RFC] Switching from glibc RPC to TI RPC Marcin Juszkiewicz
2013-03-20  9:37 ` [PATCH 1/6] eglibc: disable RPC in favour of libtirpc Marcin Juszkiewicz
2013-03-20 14:05   ` Khem Raj
2013-03-20 14:15     ` Marcin Juszkiewicz
2013-03-20  9:37 ` [PATCH 2/6] libtirpc: add RPC parts from glibc - patches from OpenMandriva Marcin Juszkiewicz
2013-03-20  9:37 ` [PATCH 3/6] busybox: disable MOUNT_NFS option - not needed on 2.6.23+ kernels Marcin Juszkiewicz
2013-03-20  9:37 ` [PATCH 4/6] quota: switch to libtirpc Marcin Juszkiewicz
2013-03-20  9:37 ` [PATCH 5/6] rpcbind: disable yellow pages support Marcin Juszkiewicz
2013-03-20  9:37 ` [PATCH 6/6] nfs-utils: switch to libtirpc Marcin Juszkiewicz
2013-03-20 10:27 ` Paul Eggleton [this message]
2013-03-20 10:41   ` [RFC] Switching from glibc RPC to TI RPC Marcin Juszkiewicz
2013-03-20 12:50     ` Mark Hatle
2013-03-20 14:09       ` Marcin Juszkiewicz
2013-03-20 14:13         ` Phil Blundell

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=1586733.G7AaCq5rbs@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=openembedded-core@lists.openembedded.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