From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9926] systemd-resolved.service: Failed at step NAMESPACE (systemd 233)
Date: Sun, 06 Aug 2017 16:25:19 +0000 [thread overview]
Message-ID: <bug-9926-163-CGl7nF6IPr@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9926-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9926
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|ASSIGNED |RESOLVED
--- Comment #5 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Mihcael, All,
I am not able to reproduce this issue with current master, with
the fiollowing defconfig (which enables the same set of systemd
options as those you listed):
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_NEON=y
BR2_ARM_ENABLE_VFP=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_INIT_SYSTEMD=y
BR2_TARGET_GENERIC_GETTY_PORT="ttyAMA0"
BR2_SYSTEM_DHCP="eth0"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.11.3"
BR2_LINUX_KERNEL_DEFCONFIG="vexpress"
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="vexpress-v2p-ca9"
BR2_PACKAGE_SYSTEMD_VCONSOLE=y
BR2_TARGET_ROOTFS_EXT2=y
# BR2_TARGET_ROOTFS_TAR is not set
Note that master contains a full rework of the skeleton to
cope with systemd.
Could you please retry on your use-case to confirm that the
bug still exists (or not!) for you with current master?
In the meantime, I am closing it. Just re-open it if you can
reproduce, in which case please attach the complete defconfig
you are using:
$ make BR2_DEFCONFIG=$(pwd)/defconfig savedefconfig
$ cat defconfig
Thanks!
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:[~2017-08-06 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 15:35 [Buildroot] [Bug 9926] New: systemd-resolved.service: Failed at step NAMESPACE (systemd 233) bugzilla at busybox.net
2017-06-01 17:44 ` Mike Williams
2017-06-02 8:47 ` [Buildroot] [Bug 9926] " bugzilla at busybox.net
2017-06-02 8:52 ` bugzilla at busybox.net
2017-06-02 9:04 ` bugzilla at busybox.net
2017-06-04 9:40 ` bugzilla at busybox.net
2017-08-06 16:25 ` bugzilla at busybox.net [this message]
2017-09-08 7:07 ` 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-9926-163-CGl7nF6IPr@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