Setting a a fixed resolv.conf file in OE built image
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.
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
Quoted 11 lines · Philip Balister
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
Quoted 12 lines
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
Signature · 4 lines
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 12 lines · Khem Raj
Quoted 11 lines · Philip Balister
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.
Quoted 4 lines
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.
Philip
Quoted 16 lines
Quoted 13 lines
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
Signature · 4 lines
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 18 lines · Philip Balister
Quoted 12 lines · Khem Raj
Quoted 11 lines · Philip Balister
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.
Quoted 4 lines
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
Quoted 5 lines
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!
Quoted 18 lines
Philip
Quoted 16 lines
Quoted 13 lines
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
Quoted 23 lines · Saul Wold
Quoted 22 lines · Philip Balister
Quoted 20 lines · Khem Raj
Quoted 4 lines
On Dec 16, 2014, at 7:12 AM, Philip Balister <[email protected]> wrote:
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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.
I did a test with core-image-minimal built for the zedboard and can confirm that I know see the expected behavior. Setting dns-nameserver in the interfaces file leads to a populated resolv.conf file.
Thanks Saul!
Philip
Quoted 29 lines
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!
Quoted 18 lines
Philip
Quoted 16 lines
Quoted 13 lines
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
Signature · 4 lines
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core