3636b40f74
The current implementation evauates the dib-init-system script too early. Also it looks that there is no simple way of getting the info about the init system automatically: another element can install (later on) a different init system. Therefore the only reliable way of setting this is manual. Change-Id: I6e9ffa1bdb3154f488f4fd335b197699b86aacd4 Signed-off-by: Andreas Florath <andreas@florath.net>
15 lines
679 B
YAML
15 lines
679 B
YAML
---
|
|
deprecations:
|
|
- |
|
|
The ``dib-init-system`` element installs a utility
|
|
``/usr/local/bin/dib-init-system`` which would try to guess the
|
|
init system (systemd, etc.). This was called from
|
|
``environment.d`` files, which means that in phases outside the
|
|
chroot it was attempting to query the init system of the build
|
|
host. This completely fails in a situation such as running inside
|
|
a container without a full init system. To avoid this issue, each
|
|
OS element will set DIB_INIT_SYSTEM directly. The
|
|
``dib-init-system`` script was not really intended to be called
|
|
directly, but will now just report the value of
|
|
``DIB_INIT_SYSTEM``.
|