Hi Nicola,
I'd like to detail the current handling of resolv.conf below.
This is the current resolv.conf handling logic.
But if you think there's something wrong about the logic, let me know.
/etc/resolv.conf would be created/written by multiple applications. In
fact, any network manager is
Hi
commit 00e4662e55f66570cae29240c22b4d74b79d3ca5
> Author: Maxin B. John
> Date: Mon Jun 12 18:10:21 2017 +0300
>
> systemd: enable resolved and networkd
>
> Enable systemd-resolved and systemd-networkd by default.
> Make it co-exist with connman and Fix associated problems
>
Hi Chen Qi,
Thanks I didn't see your previous response.
I will have a look and post my considerations.
Best Regards
Nicola Lunghi
On Mon, 16 Jul 2018 at 10:09, ChenQi wrote:
> Hi Nicola,
>
> As I replied on poky mailing list to this patch, you need to first check
> the following three commits.
Hi Nicola,
As I replied on poky mailing list to this patch, you need to first check
the following three commits.
commit 00e4662e55f66570cae29240c22b4d74b79d3ca5
Author: Maxin B. John
Date: Mon Jun 12 18:10:21 2017 +0300
systemd: enable resolved and networkd
Enable
From: Nicola Lunghi
if resolved option is not selected the package systemd-resolved
is not installed so it cannot provide an alternative for
resolv.conf
In this recipe the previous check was instead reversing the check (note the !).
This patch avoid messing with resol.conf link if resolved is
