Did you ever figure this out?
The yocto resolvconf package is missing a few things to make it actually
work like it works on other distributions. I ripped some parts out of
Debian and have it all working (although not polished).
If you want to see my .bbappend and extra files I can send them to you.
Thanks,
Dean
On 6/26/2014 4:55 AM, Alex J Lennon wrote:
On 26/06/2014 10:23, Alex J Lennon wrote:
Hi,
I'm looking at resolvconf as I want to be able to pick up dns-nameserver
changes in /etc/network/interfaces, and I'm reading that this is the way
to do it.
Having added the resolvconf package the eth0 interface is now not
correctly picking up DNS servers and putting them in /etc/resolv.conf
The behaviour is due to /etc/udhcpc.d/S50default which in the absence of
resolvconf just creates /etc/resolv.conf (which works) or if the
resolvconf binary is present it attempts to use it (which doesn't).
resolvconf looks to be using /etc/resolvconf/update.d/libc to create
/etc/resolv.conf but is crapping out as /lib/resolvconf/list-records
doesn't exist.
Is this a bug or could anybody help me to understand if there's some
other step I should be taking here?
Many thanks,
Alex
To answer my own question, I see it is a bug, and is in the process of
being addressed post-daisy -
http://article.gmane.org/gmane.comp.handhelds.openembedded.core/52463
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
