From: rdkehn at yahoo.com <rdkehn@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 0/2] package/unscd: new package
Date: Mon, 23 Nov 2015 10:32:09 -0600 [thread overview]
Message-ID: <20151123153052.GA6644@dkarchlinux64.currentcomm.com> (raw)
In-Reply-To: <5653244C.7060903@imgtec.com>
Hi Vincent,
On Mon, Nov 23, 2015 at 02:35:56PM +0000, Vicente Olivert Riera wrote:
> Dear Doug Kehn, everyone,
>
> just a small question. Perhaps I'm wrong, but..., isn't nscd deprecated
> in favor of sssd? If so, shouldn't we add the sssd package instead?
I believe [u]nscd is deprecated for RHEL/CENTOS. I'm not sure about
other distros. My Arch Linux distro installs glibc nscd by default.
I'm by no means an sssd expert; however, from a quick cursory look
http://serverfault.com/questions/534791/what-are-the-dependencies-of-sssd-nscd-to-function
it appears sssd may have dependencies that may not be desirable for
some systems. This is of course debatable.
I use unscd in my Buildroot system so I thought I would share what
is working for me since unscd was not an available package. I'm okay
with this patch not being accepted in favor of sssd.
Regards,
...doug
>
> Regards,
>
> Vincent.
>
> On 23/11/15 13:58, Doug Kehn wrote:
> > systemd recipe/support is removed. systemd support is best left to someone
> > versed in systemd who desires to use unscd with systemd.
> >
> > The BR2_GLIBC_NSCD suggestion is incorporated. However, I'm not sure what the
> > proper next steps are to properly install glibc nscd for both internal/external
> > toolchains. Is it sufficient, for now, to just define BR2_GLIBC_NSCD?
> >
> > Doug Kehn (2):
> > package/unscd: new package
> > toolchain/toolchain-common.in: install nscd
> >
> > package/Config.in | 1 +
> > package/unscd/Config.in | 11 ++++++++++
> > package/unscd/S46unscd | 24 ++++++++++++++++++++++
> > package/unscd/unscd.hash | 3 +++
> > package/unscd/unscd.mk | 47 +++++++++++++++++++++++++++++++++++++++++++
> > toolchain/toolchain-common.in | 4 ++++
> > 6 files changed, 90 insertions(+)
> > create mode 100644 package/unscd/Config.in
> > create mode 100644 package/unscd/S46unscd
> > create mode 100644 package/unscd/unscd.hash
> > create mode 100644 package/unscd/unscd.mk
> >
> > --
> > Changes v4 -> v5
> > - Reincorporate $(APPLY_PATCHES) suggestion after update by Arnout.
> > Changes v3 -> v4
> > - Incorporate feedback/suggestions by Yann and Maxime.
> > Changes v2 -> v3
> > - Remove trailing '/' from UNSCD_SITE.
> > - Whitespace cleanup.
> > Changes v1 -> v2
> > - Incorporate feedback/suggestions by Yann (from nss-pam-ldapd patch).
> >
prev parent reply other threads:[~2015-11-23 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 13:58 [Buildroot] [PATCH v5 0/2] package/unscd: new package Doug Kehn
2015-11-23 13:58 ` [Buildroot] [PATCH v5 1/2] " Doug Kehn
2015-11-30 21:44 ` Thomas Petazzoni
2015-11-30 22:17 ` Arnout Vandecappelle
2015-11-30 22:22 ` Thomas Petazzoni
2015-11-30 22:24 ` Arnout Vandecappelle
2015-11-30 22:44 ` Thomas Petazzoni
2015-12-01 13:07 ` rdkehn at yahoo.com
2015-11-23 13:58 ` [Buildroot] [PATCH v5 2/2] toolchain/toolchain-common.in: install nscd Doug Kehn
2015-11-30 22:08 ` Thomas Petazzoni
2015-11-23 14:35 ` [Buildroot] [PATCH v5 0/2] package/unscd: new package Vicente Olivert Riera
2015-11-23 16:32 ` rdkehn at yahoo.com [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=20151123153052.GA6644@dkarchlinux64.currentcomm.com \
--to=rdkehn@yahoo.com \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox