summaryrefslogtreecommitdiff
path: root/meta-quanta/meta-gsj/conf/machine/gsj.conf
diff options
context:
space:
mode:
authorAndrew Geissler <geissonator@yahoo.com>2020-05-01 22:08:32 +0300
committerAndrew Geissler <geissonator@yahoo.com>2020-05-04 19:04:12 +0300
commitf710f3f4ae86f874f47d2d77bb50508e967cfdc9 (patch)
tree79198767d3b1b8cc207950e73451c8ee0ffa5285 /meta-quanta/meta-gsj/conf/machine/gsj.conf
parentd2b10c186ec709ba03b25f8c1fcb98074ebaa580 (diff)
downloadopenbmc-f710f3f4ae86f874f47d2d77bb50508e967cfdc9.tar.xz
dunfell: sysvinit package needed for /run/lock
Upstream systemd made the inclusion of the tmpfiles.d/legacy.conf a feature that is only provided if the sysvinit PACKAGE is set. By default systemd upstream sets this but OpenBMC overrides that in this file. The legacy.conf provides among other things, a creation of the /run/lock directory. Applications like fw_printenv and fw_setenv rely on the /run/lock directory being present. opened systemd/systemd#15668 to see if there could be a more efficient way of getting /run/lock. Tying it to sysvinit and having it in a file called legacy.conf just doesn't make a lot of sense to me. Tested: Verified /run/lock is now present in QEMU boot and that fw_printenv worked. (From meta-phosphor rev: 561141712e568d555de414363b1115f37fe2cfce) Change-Id: I32b3560b30a2743638bfe1402ba3c72203b4ab0b Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'meta-quanta/meta-gsj/conf/machine/gsj.conf')
0 files changed, 0 insertions, 0 deletions