From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9881] New: systemd-resolved not setting resolv.conf link
Date: Wed, 17 May 2017 12:46:42 +0000 [thread overview]
Message-ID: <bug-9881-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9881
Bug ID: 9881
Summary: systemd-resolved not setting resolv.conf link
Product: buildroot
Version: 2017.02.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: posted at heine.so
CC: buildroot at uclibc.org
Target Milestone: ---
I have a configuration with Network-Manager and systemd-resolved but without
systemd-networkd.
This leads to a system with an invalid resolv.conf configuration.
The built system still has this configuration from skeleton:
/etc/resolv.conf -> ../tmp/resolv.conf
systemd is not touching /etc/resolv.conf since it exists (but points to
nothing.)
the systemd.mk defines this:
define SYSTEMD_INSTALL_RESOLVCONF_HOOK
ln -sf ../run/systemd/resolve/resolv.conf \
$(TARGET_DIR)/etc/resolv.conf
endef
But this is only used when systemd-networkd is selected. I guess this should
also be done when only BR2_PACKAGE_SYSTEMD_RESOLVED is selected.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-05-17 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 12:46 bugzilla at busybox.net [this message]
2017-08-02 19:55 ` [Buildroot] [Bug 9881] systemd-resolved not setting resolv.conf link bugzilla at busybox.net
2019-08-11 19:13 ` bugzilla at busybox.net
2019-08-11 19:41 ` bugzilla at busybox.net
2019-10-26 17:04 ` bugzilla at busybox.net
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=bug-9881-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.