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>
18 lines
541 B
ReStructuredText
18 lines
541 B
ReStructuredText
===============
|
|
dib-init-system
|
|
===============
|
|
|
|
Element that handles aspects of the used target's init system.
|
|
|
|
Any files placed in a ``init-scripts/INIT_SYSTEM`` directory inside the
|
|
element will be copied into the appropriate directory if ``INIT_SYSTEM``
|
|
is in use on the host.
|
|
|
|
Environment Variables
|
|
---------------------
|
|
|
|
DIB_INIT_SYSTEM
|
|
:Description: One of ``upstart``, ``systemd``, ``openrc`` or
|
|
``sysv`` depending on the init system in use for the target image.
|
|
This should be set automatically by your platform elements.
|