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: Fri, 02 Jun 2017 08:52:40 +0000 [thread overview]
Message-ID: <bug-9926-163-MKX63T2iDv@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9926-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9926
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
When Buildroot builds the kernel itself, and systemd is enabled, it makes sure
a number of options are enabled. From linux/linux.mk:
$(if $(BR2_PACKAGE_SYSTEMD),
$(call KCONFIG_ENABLE_OPT,CONFIG_CGROUPS,$(@D)/.config)
$(call KCONFIG_ENABLE_OPT,CONFIG_INOTIFY_USER,$(@D)/.config)
$(call KCONFIG_ENABLE_OPT,CONFIG_FHANDLE,$(@D)/.config)
$(call KCONFIG_ENABLE_OPT,CONFIG_AUTOFS4_FS,$(@D)/.config)
$(call KCONFIG_ENABLE_OPT,CONFIG_TMPFS_POSIX_ACL,$(@D)/.config)
$(call
KCONFIG_ENABLE_OPT,CONFIG_TMPFS_POSIX_XATTR,$(@D)/.config))
Can you check if you have all those options enabled in your kernel
configuration?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-06-02 8:52 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 [this message]
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
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-MKX63T2iDv@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