[oe] [meta-networking][Patch] Revert "networkmanager: Use ALTERNATIVES for resolv-conf handling."

[Drew Moseley]

On 9/1/19 8:59 PM, kai.kang at windriver.com wrote:
> From: Kai Kang <kai.kang at windriver.com>
>
> This reverts commit 3982dc5b1994ffcc52336b02fbd2c44db164dd82.
>
> With this commit it creates link file /etc/resolv.conf via
> update-alternatives but the target doesn't exist.
>
> On target:
>
> root at qemux86-64:~# ls -l /etc/resolv*
> lrwxrwxrwx    1 root     root            33 Aug 27 09:17 /etc/resolv-conf.NetworkManager -> ../run/NetworkManager/resolv.conf
> lrwxrwxrwx    1 root     root            34 Aug 23 03:08 /etc/resolv-conf.systemd -> ../run/systemd/resolve/resolv.conf
> lrwxrwxrwx    1 root     root            31 Aug 27 09:22 /etc/resolv.conf -> /etc/resolv-conf.NetworkManager
>
> root at qemux86-64:~# ls -l /run/NetworkManager/resolv.conf
> ls: /run/NetworkManager/resolv.conf: No such file or directory
>
> root at qemux86-64:~# cat /etc/resolv.conf
> cat: can't open '/etc/resolv.conf': No such file or directory
>
(Apologies for the delay in getting back to this)

Interestingly, in rocko, the /var/run/NetworkManager/resolv.conf file is
automatically generated but in thud it does not seem to be.  Without
this patch, we are relying on /var/run/systemd/resolv.conf existing even
when not using systemd for name resolution. I wonder if the right
solution is to figure out why the /var/run/NetworkManager/resolv.conf
file is no longer created.


Drew

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pEpkey.asc
Type: application/pgp-keys
Size: 2464 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20190903/db71b66e/attachment.bin>