From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] samba: Add support for libnss_win*.so* installation
Date: Mon, 24 Nov 2014 20:34:53 +0100 [thread overview]
Message-ID: <20141124203453.59c5f279@free-electrons.com> (raw)
In-Reply-To: <54730753.3030108@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 24 Nov 2014 07:24:19 -0300, Gustavo Zacarias wrote:
> > I must say I'm a bit skeptical about two things (about which probably
> > Beno?t can give some details) :
> >
> > * The usefulness of enabling the NSS libraries in non-glibc
> > environments. Even though I agree that technically, nothing prevents
> > some program from using them, in practice, the NSS libraries are
> > basically only used by the glibc name resolution logic. So I would
> > personally prefer to make those NSS libraries visible only in glibc
> > configurations.
>
> Even if they can be built they really are intended for (e)glibc so we agree.
> If you need to access/use wbclient functionality you could just use the
> wbclient (winbind) api by enabling samba install to staging, that's the
> public way of accessing it.
Agreed.
> > * The fact that the winbindd daemon is not actually needed on the
> > target to get libnss_wins/libnss_winbind working. My understanding
> > is that winbindd is a daemon that will answer to the name resolution
> > requests of libnss_wins/libnss_winbind, so I don't see how they can
> > work without the daemon running.
>
> AFAIK you need winbind running in order to use libwbclient and/or
> libnss_winbind/wins. I think libnss_wins has a fallback to DNS-only mode
> but it's probably not very useful.
Ok.
Beno?t, can you rework your patches to take into account those comments?
> Also please note that Samba 3 is very likely going EOL as soon as Samba
> 4.2.x is released which even though delayed a bit in the RC phase is
> coming along pretty soon, so adding feature to the samba3 package isn't
> very wise IMHO (it's in security-only fixes now).
> See: https://wiki.samba.org/index.php/Samba_Release_Planning
Ok. Still there's some chance that we will keep Samba 3 around for a
bit of time, just like we still have libgtk2 available.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-24 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 18:14 [Buildroot] [PATCH 1/2] samba: Remove execution rights from smb.conf Benoît Thébaudeau
2014-08-04 18:14 ` [Buildroot] [PATCH 2/2] samba: Add support for libnss_win*.so* installation Benoît Thébaudeau
2014-08-04 18:28 ` Thomas Petazzoni
2014-08-04 18:37 ` Benoît Thébaudeau
2014-11-22 20:33 ` Thomas Petazzoni
2014-11-24 10:24 ` Gustavo Zacarias
2014-11-24 19:34 ` Thomas Petazzoni [this message]
2014-11-24 21:05 ` Benoît Thébaudeau
2014-11-24 21:09 ` Gustavo Zacarias
2014-08-04 18:27 ` [Buildroot] [PATCH 1/2] samba: Remove execution rights from smb.conf Thomas Petazzoni
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=20141124203453.59c5f279@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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