From bfa769d185dab1d2e4d63cedca16e6fc96ddad8c Mon Sep 17 00:00:00 2001 From: =?utf8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Fri, 30 Sep 2022 15:31:40 +0200 Subject: [PATCH] man: add cross-links about preset operations --- man/machine-id.xml | 3 ++- man/systemd.preset.xml | 16 ++++++++++------ man/systemd.xml | 9 +++++++-- 3 files changed, 19 insertions(+), 9 deletions(-) diff --git a/man/machine-id.xml b/man/machine-id.xml index b40e26bbabe..ec1ab64dec1 100644 --- a/man/machine-id.xml +++ b/man/machine-id.xml @@ -147,7 +147,8 @@ If according to the above rules a first boot is detected, units with - ConditionFirstBoot=yes will be run. + ConditionFirstBoot=yes will be run and systemd will perform + additional initialization steps, in particular presetting units. diff --git a/man/systemd.preset.xml b/man/systemd.preset.xml index 9e6db28536b..ab730d2cc21 100644 --- a/man/systemd.preset.xml +++ b/man/systemd.preset.xml @@ -47,12 +47,16 @@ units, but rather centralize them in a distribution or spin default policy, which can be amended by administrator policy, see below. - If no preset files exist, systemctl - preset will enable all units that are installed by - default. If this is not desired and all units shall rather be - disabled, it is necessary to ship a preset file with a single, - catchall "disable *" line. (See example 1, - below.) + If no preset files exist, preset operations will enable all units that are installed by default. If + this is not desired and all units shall rather be disabled, it is necessary to ship a preset file with a + single, catchall "disable *" line. (See example 1, below.) + + When the machine is booted for the first time, + systemd1 will + enable/disable all units according to preset policy, similarly to systemctl + preset-all. Also see "First Boot Semantics" in + machine-id5. + diff --git a/man/systemd.xml b/man/systemd.xml index f4213e2ee84..1a68301d50b 100644 --- a/man/systemd.xml +++ b/man/systemd.xml @@ -188,8 +188,13 @@ systemd.special7 for details about these target units. - systemd only keeps a minimal set of units loaded into memory. Specifically, the only units that are kept - loaded into memory are those for which at least one of the following conditions is true: + On first boot, systemd will enable or disable units according to preset policy. + See systemd.preset5 + and "First Boot Semantics" in + machine-id5. + + systemd only keeps a minimal set of units loaded into memory. Specifically, the only units that are + kept loaded into memory are those for which at least one of the following conditions is true: It is in an active, activating, deactivating or failed state (i.e. in any unit state except for inactive) -- 2.47.3