[Buildroot] ping not working in a glibc based buildroot

Eial Czerwacki eial at scalemp.com
Sun Jul 13 06:37:52 UTC 2014


Greetings Yann,

On 07/10/2014 07:30 PM, Yann E. MORIN wrote:
> Eial, All,
>
> I know you solved your issue by copying the missing NSS libs,
> yet I have a comment about this mail, see below.
>
> On 2014-07-10 15:15 +0300, Eial Czerwacki spake thusly:
>> On 07/09/2014 05:53 PM, Eial Czerwacki wrote:
>>> Greetings Gustavo,
>>>
>>> On 07/09/2014 05:46 PM, Gustavo Zacarias wrote:
>>>> On 07/09/2014 11:40 AM, Eial Czerwacki wrote:
>>>>
>>>>> yes, here it is:
>>>>> --- /etc/resolv.conf    2014-07-09 17:35:30.420040438 +0300
>>>>> +++ yyy/etc/resolv.conf 1970-01-01 02:00:00.000000000 +0200
>>>>> @@ -1,3 +0,0 @@
>>>>> -; generated by /sbin/dhclient-script
>>>>> -search cluserdns cluserdnsus
>>>>> -nameserver 10.100.1.40
>>>>>
>>>>> thing is, I'm not sure who generates the content of that file, is it
>>>>> part of busybox? other utility?
>>>> That depends on your network configuration, for static IP scenarios
>>>> normally you do, for DHCP it's normally done by the dhcp post up script.
>>>> Regards.
>>>>
>>>>
>>>>
>>> did you mean /usr/share/udhcpc/default.script?
>> I've looked into the resolv.conf of the actual boot (not chroot) and I
>> saw the domain bad issue (bug #3979), applying it gave me valid domain
>> again in resolv.conf but problem still persists.
>>
>> it is like udhcpc cannot find the dns servers. am I right? where do we
>> set dns?
> When you are in a chroot, you are still using the IP stack from your
> non-chroot system, so the network interfaces are already configured.
> So, no need to run a DHCP client.
>
> However, you still need to properly setup the resolver in your chroot,
> which you did by filling in /etc/resolv.conf and copying the NSS libs.
>
> For example, I usually just copy the non-chroot /etc/resolv.conf into my
> chroot.
>
> Regards,
> Yann E. MORIN.
>
that is correct when to comes to chrooting into the image but I'm not
sure that the same resolv.conf will be suited to boot from that same img.

Eial.



More information about the buildroot mailing list