From: Trent Piepho <tpiepho@impinj.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/skeleton-init-systemd: create a symlink /var/run to ../run
Date: Tue, 27 Feb 2018 18:37:54 +0000 [thread overview]
Message-ID: <1519756674.25567.181.camel@impinj.com> (raw)
In-Reply-To: <594ebd6a-1bb7-9b97-66af-d55344f8c8e9@gmail.com>
On Sun, 2018-02-25 at 20:16 +0100, Romain Naour wrote:
> The file /usr/lib/tmpfiles.d/var.con will create automatically that
> > > symlink at bootup /var/run doesn't exist yet. But dbus creates, at
> > > install time, the directory /var/run/dbus without taking care of
> > > /var/run. So we end up with two different directories /run and
> > > /var/run. This bug affects more or less all systemd-provided
> > > utilities, including logind and systemd itself.
> > >
> > > This patch create the correct symlink run -> ../run when systemd
> > > is used as init system.
> >
> > This doesn't work in the RO root case.
>
> Indeed, but I'm testing/fixing the RW case with this patch
> (BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW).
I should have said that differently. RO root has the same problem, but
this link will not solve it.
I believe the link:
ln -sf ../../../../run $(TARGET_DIR)/usr/share/factory/var/run
will fix the RO case. But of course does not work in the RW case.
I can send a follow on patch to add this link for RO.
But I wish there was some other method that could solve the problem for
both RW and RO, without needing to add special cases like this link.
next prev parent reply other threads:[~2018-02-27 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 22:10 [Buildroot] [PATCH] package/skeleton-init-systemd: create a symlink /var/run to ../run Romain Naour
2018-02-23 18:25 ` Trent Piepho
2018-02-24 18:15 ` Arnout Vandecappelle
2018-02-27 19:28 ` Trent Piepho
2018-02-25 19:16 ` Romain Naour
2018-02-27 18:37 ` Trent Piepho [this message]
2018-02-27 21:24 ` Pierre
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=1519756674.25567.181.camel@impinj.com \
--to=tpiepho@impinj.com \
--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