diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 768700a277..544a14693a 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3080,13 +3080,37 @@
By default, the Yocto Project uses
SysVinit as the initialization manager.
- However, support also exists for systemd.
+ However, support also exists for systemd,
+ which is a full replacement of for init with
+ parallel starting of services, reduced shell overhead and other
+ features, used by many distributions.
+
+
+
If you want to use SysVinit, you do
not have to do anything.
But, if you want to use systemd, you must
take some steps as described in the following sections.
+
+ NOTES TO SELF:
+ systemd is a full replacement of for init with
+ parallel starting of services, reduced shell overhead and other
+ features, used by many distributions.
+ I think you set the VIRTUAL-RUNTIME
+ in a recipe.
+ I found a recipe called
+ packagegroup-core-boot.bb, which is an
+ OE-Core recipe, that has a bunch of them.
+ The comment refers to the group as "VIRTUAL-RUNTIME providers".
+ The list includes VIRTUAL-RUNTIME_dev_manager,
+ VIRTUAL-RUNTIME_init_manager,
+ VIRTUAL-RUNTIME_login_manager,
+ VIRTUAL-RUNTIME_initscripts, and
+ VIRTUAL-RUNTIME_keymaps.
+
+
Using systemd Exclusively
@@ -3118,8 +3142,8 @@
DISTRO_FEATURES = "systemd"
VIRTUAL-RUNTIME_init-manager = "systemd"
- Doing so causes your main image to use
- packagegroup-core-boot and
+ Doing so causes your main image to use the
+ packagegroup-core-boot.bb recipe and
systemd.
The rescue/minimal image cannot use this group.
However, it can install sysvinit