From: Patrick Ohly <patrick.ohly@intel.com>
To: "Maxin B. John" <maxin.john@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] systemd: enable resolved and networkd
Date: Thu, 06 Jul 2017 17:12:05 +0200 [thread overview]
Message-ID: <1499353925.5278.21.camel@intel.com> (raw)
In-Reply-To: <1497280222-11549-2-git-send-email-maxin.john@intel.com>
On Mon, 2017-06-12 at 18:10 +0300, Maxin B. John wrote:
> Enable systemd-resolved and systemd-networkd by default.
> Make it co-exist with connman and Fix associated problems
> in read-only rootfs.
>
> Fixes [YOCTO #11331]
Let me come back to this, because I think it is not quite working as
intended yet.
The goal is that the "right" resolver is chosen via alternative
priorities, right? So during build time, we set /etc/resolv.conf to what
is the desired resolver.
However, there's still a L+ entry for /etc/resolv.conf
in /usr/lib/tmpfiles.d/connman_resolvconf.conf:
L+ /etc/resolv.conf - - - - /var/run/connman/resolv.conf
As a result, when systemd is used and the rootfs is read/write, then
systemd overwrites /etc/resolv.conf, leading to:
# ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 28 Jul 6 14:44 /etc/resolv.conf -> /var/run/connman/resolv.conf
That happens even if systemd-resolved has a higher priority and should
be used.
Maxin, do you agree? Can you finish this work and patch the ConnMan
recipe so that it behaves as expected?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-07-06 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 15:10 [PATCH 0/2] [RFC] fix systemd-resolved and connman boot in read only rootfs Maxin B. John
2017-06-12 15:10 ` [PATCH 1/2] systemd: enable resolved and networkd Maxin B. John
2017-07-06 15:12 ` Patrick Ohly [this message]
2017-07-07 8:10 ` Maxin B. John
2017-06-12 15:10 ` [PATCH 2/2] connman: correct the systemd boot in read only rootfs Maxin B. John
2017-11-24 12:03 ` Patrick Ohly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1499353925.5278.21.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=maxin.john@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox