From: "kai" <kai.kang@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] systemd.bbclass: check whether systemctl works in
Date: Thu, 29 Oct 2020 17:26:49 +0800 [thread overview]
Message-ID: <20201029092650.34868-1-kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
It fails to run systemctl in a container even though it exists. Check
with 'systemctl list-machines' to make sure systemctl works.
And there is another issue that /var/tmp is a dead link to volatile/tmp
which doesn't exists. Changqing has sent a patch to fix it. My concern
is in FHS, /var/tmp should not volatile. Could we make /var/tmp as a
common directory rather than a link without extra config?
Ref:
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s15.html
Kai Kang (1):
systemd.bbclass: check whether systemctl works in post scripts
meta/classes/systemd.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2020-10-29 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 9:26 kai [this message]
2020-10-29 9:26 ` [PATCH 1/1] systemd.bbclass: check whether systemctl works in post scripts kai
2020-10-29 9:48 ` [OE-core] " Andreas Oberritter
2020-10-30 5:44 ` 回复: " kai
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=20201029092650.34868-1-kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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