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.

Change-Id: Ib508ec05b71eba6173b9f3552b02260ace5c5a69
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: ac1c523671e601d4cc53883a403ccd1fc1b1d84f
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. recipes-x86/
  16. COPYING.apache-2.0
  17. COPYING.MIT
  18. LICENSE
  19. MAINTAINERS
  20. README.md
  21. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.