dev/ref-manual: Document INIT_MANAGER

The INIT_MANAGER variable was added in 3.0 but it seems we didn't get
around to documenting it yet. I have added a variable glossary entry and
made the basic adjustment of the "Using systemd Exclusively" section in
the dev manual, however I think the latter section still needs work.

(From yocto-docs rev: 602c0e8f770516256dab04edfd887377303c06bb)

Signed-off-by: Paul Eggleton <bluelightning@bluelightning.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Paul Eggleton
2023-04-22 15:19:50 +12:00
committed by Richard Purdie
parent eb292619e7
commit ea2feb23bc
2 changed files with 21 additions and 18 deletions

View File

@@ -38,26 +38,14 @@ following sections.
Using systemd Exclusively Using systemd Exclusively
========================= =========================
Set these variables in your distribution configuration file as follows:: Set the :term:`INIT_MANAGER` variable in your distribution configuration
file as follows::
DISTRO_FEATURES:append = " systemd" INIT_MANAGER = "systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
You can also prevent the SysVinit distribution feature from This will enable systemd and remove sysvinit components from the image.
being automatically enabled as follows:: See ``meta/conf/distro/include/init-manager-systemd.inc`` for exact
details on what this does.
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
Doing so removes any
redundant SysVinit scripts.
To remove initscripts from your image altogether, set this variable
also::
VIRTUAL-RUNTIME_initscripts = ""
For information on the backfill variable, see
:term:`DISTRO_FEATURES_BACKFILL_CONSIDERED`.
Using systemd for the Main Image and Using SysVinit for the Rescue Image Using systemd for the Main Image and Using SysVinit for the Rescue Image
======================================================================== ========================================================================

View File

@@ -3956,6 +3956,21 @@ system and gives an overview of their function and contents.
even if the toolchain's binaries are strippable, there are other files even if the toolchain's binaries are strippable, there are other files
needed for the build that are not strippable. needed for the build that are not strippable.
:term:`INIT_MANAGER`
Specifies the system init manager to use. Available options are:
- ``sysvinit`` - System V init (default for poky)
- ``systemd`` - systemd
- ``mdev-busybox`` - mdev provided by busybox
- ``none`` - no init manager
More concretely, this is used to include
``conf/distro/include/init-manager-${INIT_MANAGER}.inc`` into the global
configuration. You can have a look at the ``conf/distro/include/init-manager-*.inc``
files for more information, and also the
":ref:`dev-manual/init-manager:selecting an initialization manager`"
section in the Yocto Project Development Tasks Manual.
:term:`INITRAMFS_DEPLOY_DIR_IMAGE` :term:`INITRAMFS_DEPLOY_DIR_IMAGE`
Indicates the deploy directory used by :ref:`ref-tasks-bundle_initramfs` Indicates the deploy directory used by :ref:`ref-tasks-bundle_initramfs`
where the :term:`INITRAMFS_IMAGE` will be fetched from. This variable is where the :term:`INITRAMFS_IMAGE` will be fetched from. This variable is