From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] [Jan Kundrát] [PATCH 1/3] systemd: Ensure /run and /var/run are the same on R/O rootfs
Date: Wed, 14 Feb 2018 18:13:37 -0500 [thread overview]
Message-ID: <87eflnyxjy.fsf@paral.in> (raw)
In-Reply-To: <87k1vfz2m4.fsf@paral.in>
Hi Jan, all,
> From: Jan Kundr?t <jan.kundrat@cesnet.cz>
> I'm leaving that one to someone who is more familiar with systemd and
> buildroot conventions. My box now boots again, so I'm happy :).
>
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=101628
>
> Signed-off-by: Jan Kundr?t <jan.kundrat@cesnet.cz>
> ---
> package/skeleton-init-systemd/skeleton-init-systemd.mk | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/package/skeleton-init-systemd/skeleton-init-systemd.mk b/package/skeleton-init-systemd/skeleton-init-systemd.mk
> index a2d4e8c4b3..95142904f5 100644
> --- a/package/skeleton-init-systemd/skeleton-init-systemd.mk
> +++ b/package/skeleton-init-systemd/skeleton-init-systemd.mk
> @@ -42,7 +42,9 @@ define SKELETON_INIT_SYSTEMD_PRE_ROOTFS_VAR
> mkdir $(TARGET_DIR)/var
> for i in $(TARGET_DIR)/usr/share/factory/var/*; do \
> j="$${i#$(TARGET_DIR)/usr/share/factory}"; \
> - if [ -L "$${i}" ]; then \
> + if [ "$${j}" = "/var/run" ]; then \
> + echo "# $${j} is being handled by systemd"
> + elif [ -L "$${i}" ]; then \
> printf "L+! %s - - - - %s\n" \
> "$${j}" "../usr/share/factory/$${j}" \
> || exit 1; \
> --
> 2.14.3
>
I applied this patch, thanks. Unfortunately, it seems the problem is
still occurring. Maybe it's a different problem?
[ 16.650294] systemd[1]: System is tainted: var-run-bad
[ 16.680724] systemd[1]: Starting Network Connectivity...
[ 16.710421] systemd[1]: Started D-Bus System Message Bus.
[ 16.740678] systemd[1]: Failed to connect to system bus: No such file or directory
[ 16.770425] systemd[1]: Failed to initialize D-Bus connection: No such file or directory
[ 16.800386] systemd[1]: Starting Network Manager...
[1518648890.7497] hostname: hostname: hostnamed not used as proxy creation failed
[ 39.020736] dbus-daemon[314]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
[ 39.100451] dbus-daemon[314]: [system] Activating systemd to hand-off: service name='org.freedesktop.nm
_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.0' (uid=0 pid=315 comm="/u
sr/sbin/NetworkManager --no-daemon ")
[ 39.150403] NetworkManager[315]: <info> [1518648890.7540] manager[0x20ac030]: rfkill: WWAN hardware ra
It seems that systemd still cannot talk to the system bus.
I can also see this happening if I try to execute systemd-hostnamed:
# ./systemd-hostnamed
Failed to get system bus connection: No such file or directory
# ls /var/run/
NetworkManager dhcpcd.pid docker ifstate utmp
dbus dhcpcd.sock docker.pid sepermit
dhcpcd dhcpcd.unpriv.sock docker.sock sshd.pid
# ls /var/run/dbus
system_bus_socket
# ls /run/
blkid lock mount systemd user xtables.lock
docker log ntpd.pid udev utmp
If I link dbus like so:
# ln -s /var/run/dbus/ /run/dbus
It seems then that everything works fine.
~ Christian
next parent reply other threads:[~2018-02-14 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k1vfz2m4.fsf@paral.in>
2018-02-14 23:13 ` Christian Stewart [this message]
2018-02-15 12:42 ` [Buildroot] [Jan Kundrát] [PATCH 1/3] systemd: Ensure /run and /var/run are the same on R/O rootfs Jan Kundrát
2018-02-21 22:30 ` Christian Stewart
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=87eflnyxjy.fsf@paral.in \
--to=christian@paral.in \
--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