From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13271] systemd-resolved: /etc/resolv.conf link broken on per-package build
Date: Sat, 27 Mar 2021 21:11:06 +0000 [thread overview]
Message-ID: <bug-13271-163-lhTgpBoKw4@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13271-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13271
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Michael, All,
> define SYSTEMD_INSTALL_RESOLVCONF_HOOK
> ln -sf ../run/systemd/resolve/resolv.conf \
> $(TARGET_DIR)/etc/resolv.conf
> endef
> [...]
> SYSTEMD_POST_INSTALL_TARGET_HOOKS += \
> SYSTEMD_INSTALL_RESOLVCONF_HOOK
Indeed, a hook doing such changes should be made to be a target-fianlize
hook rather than a post-target-install hook.
In systemd, there is already a target-finalize hook, for the nsswitch
configuration file.
Care to send a patch, please?
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-27 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 13:53 [Buildroot] [Bug 13271] New: systemd-resolved: /etc/resolv.conf link broken on per-package build bugzilla at busybox.net
2021-03-25 20:38 ` [Buildroot] [Bug 13271] " bugzilla at busybox.net
2021-03-25 20:49 ` bugzilla at busybox.net
2021-03-27 21:11 ` bugzilla at busybox.net [this message]
2021-04-13 19:16 ` 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-13271-163-lhTgpBoKw4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox