diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2024-02-07 13:47:38 +0100 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2024-02-08 20:36:44 +0100 |
| commit | eb470316943f07e382371ee4326ff6442156a07b (patch) | |
| tree | 0c3f3ac5b155e46d0bfe41e474c6e1ff33160814 /man/systemd.unit.xml | |
| parent | creds: fix typo (diff) | |
| download | systemd-eb470316943f07e382371ee4326ff6442156a07b.tar.xz systemd-eb470316943f07e382371ee4326ff6442156a07b.zip | |
man: mention that preset-all is performed during early boot
The intro of systemd-firstboot is rewritten to make it clearer how it fits into
the big picture. Systemd does some machine-id and presets and
systemd-firstboot.service is used to interactively fill in the blanks.
Closes #22225.
Diffstat (limited to 'man/systemd.unit.xml')
| -rw-r--r-- | man/systemd.unit.xml | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index f7a6af7059..46184f5b7e 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -1654,12 +1654,20 @@ whether the system is booting up for the first time. This roughly means that <filename>/etc/</filename> was unpopulated when the system started booting (for details, see "First Boot Semantics" in <citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry>). - First boot is considered finished (this condition will evaluate as false) after the manager + First Boot is considered finished (this condition will evaluate as false) after the manager has finished the startup phase.</para> <para>This condition may be used to populate <filename>/etc/</filename> on the first boot after factory reset, or when a new system instance boots up for the first time.</para> + <para>Note that the service manager itself will perform setup steps during First Boot: it will + initialize + <citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry> and + preset all units, enabling or disabling them according to the + <citerefentry><refentrytitle>systemd.preset</refentrytitle><manvolnum>5</manvolnum></citerefentry> + settings. Additional setup may be performed via units with + <varname>ConditionFirstBoot=yes</varname>.</para> + <para>For robustness, units with <varname>ConditionFirstBoot=yes</varname> should order themselves before <filename>first-boot-complete.target</filename> and pull in this passive target with <varname>Wants=</varname>. This ensures that in a case of an aborted first boot, these units will |