summaryrefslogtreecommitdiffstats
path: root/man/systemd-firstboot.xml
diff options
context:
space:
mode:
authorMike Yuan <me@yhndnzj.com>2023-09-25 19:01:57 +0200
committerMike Yuan <me@yhndnzj.com>2023-09-25 19:01:57 +0200
commitff4a7d32f11f765b9babbdfff37db911c8bdea60 (patch)
tree6526f85ab153fa4177febe9fa7a285ae52088621 /man/systemd-firstboot.xml
parentcore/main: log that we assume first boot if failed to read machine-id (diff)
downloadsystemd-ff4a7d32f11f765b9babbdfff37db911c8bdea60.tar.xz
systemd-ff4a7d32f11f765b9babbdfff37db911c8bdea60.zip
man/systemd-firstboot: /etc/ empty -> unpopulated
We use the phrase "unpopulated" in systemd.unit(5) too. And "/etc/ is empty" is simply spurious.
Diffstat (limited to 'man/systemd-firstboot.xml')
-rw-r--r--man/systemd-firstboot.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/systemd-firstboot.xml b/man/systemd-firstboot.xml
index 3aa160ecad..5129d068f2 100644
--- a/man/systemd-firstboot.xml
+++ b/man/systemd-firstboot.xml
@@ -37,7 +37,7 @@
<para><command>systemd-firstboot</command> initializes basic system settings interactively during the
first boot, or non-interactively on an offline system image. The service is started during boot if
<varname>ConditionFirstBoot=yes</varname> is met, which essentially means that <filename>/etc/</filename>
- is empty, see
+ is unpopulated, see
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
details.</para>