On 12/16/2014 08:55 AM, Philip Balister wrote:
On 12/16/2014 11:40 AM, Khem Raj wrote:
On Dec 16, 2014, at 7:12 AM, Philip Balister <[email protected]> wrote:
Any tips on how to do this the right way? It seems like fixed
resolv.conf's are no longer fashionable and the volatile.cache script
goes to great lengths to reset it.
Adding a dns-nameserver entry in the interfaces file never makes it to
resolv.conf. I tried installing the resolvconf package and played with
it, but no joy. This package also appears to have some issues with
missing pieces.
depends a lot on what package combination you are using. If its systemd and you
are using systemd-resolved then it generates resolve.conf in /run/ and symlink
in /etc/ gets the job done. if its udhcpc then it will populate the one in /etc
and it will take interfaces file in /etc into consideration
Yeah, but this is an image built by adding packages to core-image. No
systemd or other network managers. It feels like just adding the
dns-nameserver line to interfaces should work, but something appears to
not re-populate resolv.conf after it is wiped at boot.
I recently sent some patches to this area, dealing with all the dhcp
clients and resolvconf package.
Can you enumerate which networking tools you have installed, if you are
not using any network manager or dhcp client and relying on a static
dns-nameserver entry, you might need resolvconf if you are not using it.
Also which version of oe-core meta-data are you using?
Sau!
Philip
I'll file bugs, but until I can figure out how it is suposed to work,
any bug I file is going to be pretty vague.
This really should be easier.
Philip
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
