Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] ping not working in a glibc based buildroot
Date: Thu, 10 Jul 2014 23:18:05 +0200	[thread overview]
Message-ID: <20140710211805.GI28300@free.fr> (raw)
In-Reply-To: <53BEA249.3020808@scalemp.com>

Eial, All,

On 2014-07-10 17:25 +0300, Eial Czerwacki spake thusly:
> On 07/10/2014 05:16 PM, Thomas Petazzoni wrote:
> > Dear Eial Czerwacki,
> >
> > On Thu, 10 Jul 2014 17:13:57 +0300, Eial Czerwacki wrote:
> >
> >> I've added libnss_dns-2.18.so to the img and libresolv.so and it seems
> >> to be working.
> >> the files are missing because I work in a kinda limited size.
> > So you removed them manually? I'd like to understand what happened, to
> > fix Buildroot if needed.
> >
> >> do I need the other libnss_*.so files?
> > By default, we only copy libnss_dns (to do DNS resolution) and
> > libnss_files (to do /etc/hosts based resolution), and we don't copy the
> > other libnss_* libraries, which are used for more advanced name
> > resolution that are generally not used on most embedded systems.
> >
> > See 'man nsswitch.conf' for more details.
> >
> > Best regards,
> >
> > Thomas
> I see, as I don't use /etc/hosts, I think I don't need libnss_files.

The NSS libraries are not used only to provide DNS resolving.

They are used to do any kind of name lookups:
  - IP <-> hostname mapping (as already mentioned),
  - UID <-> username mapping,
  - gid <-> group name mapping,
  - and a bunch more. See the complete list:  man nsswitch.conf

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-07-10 21:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 13:28 [Buildroot] ping not working in a glibc based buildroot Eial Czerwacki
2014-07-09 14:22 ` Baruch Siach
2014-07-09 14:40   ` Eial Czerwacki
2014-07-09 14:46     ` Gustavo Zacarias
2014-07-09 14:53       ` Eial Czerwacki
2014-07-10 12:15         ` Eial Czerwacki
2014-07-10 12:23           ` Thomas Petazzoni
2014-07-10 12:35             ` Eial Czerwacki
2014-07-10 12:56               ` Thomas Petazzoni
2014-07-10 13:02                 ` Eial Czerwacki
2014-07-10 13:34                   ` Thomas Petazzoni
2014-07-10 13:40                     ` Eial Czerwacki
2014-07-10 14:06                       ` Thomas Petazzoni
2014-07-10 14:13                         ` Eial Czerwacki
2014-07-10 14:16                           ` Thomas Petazzoni
2014-07-10 14:25                             ` Eial Czerwacki
2014-07-10 21:18                               ` Yann E. MORIN [this message]
2014-07-10 14:24                           ` Baruch Siach
2014-07-10 14:34                             ` Eial Czerwacki
2014-07-10 16:30           ` Yann E. MORIN
2014-07-13  6:37             ` Eial Czerwacki

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=20140710211805.GI28300@free.fr \
    --to=yann.morin.1998@free.fr \
    --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