morgan/systemd
1
0
Fork 0
mirror of https://github.com/morgan9e/systemd synced 2026-04-14 00:14:32 +09:00
Code Issues Packages Projects Releases Wiki Activity

man: encourage the creation of empty machine-id instead of deleting it

Browse Source 
Current text hints that machine-id in template image should be empty
if the system is read-only. But most of the bare metal systems and
regular VMs have /etc read-only at this phase of boot.
This commit is contained in:
Lukas Nykryn
2025-06-18 13:33:25 +02:00
committed by Zbigniew Jędrzejewski-Szmek
parent ea71d34738
commit 64fcb07199
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
man/machine-id.xml
View File

@@ -84,9 +84,9 @@
containers or in the cloud, <filename>/etc/machine-id</filename> should be either missing or an empty
file in the generic file system image (the difference between the two options is described under "First
Boot Semantics" below). An ID will be generated during boot and saved to this file if possible. Having an
empty file in place is useful because it allows a temporary file to be bind-mounted over the real file,
in case the image is used read-only. Also see <ulink url="https://systemd.io/BUILDING_IMAGES">Safely
Building Images</ulink>.</para>
empty file in place is recommended because it allows a temporary file to be bind-mounted over the real file,
in case the image is used read-only and when <filename>/etc</filename> is mounted read-only in the early boot.
Also see <ulink url="https://systemd.io/BUILDING_IMAGES">Safely Building Images</ulink>.</para>
<para><citerefentry><refentrytitle>systemd-firstboot</refentrytitle><manvolnum>1</manvolnum></citerefentry>
may be used to initialize <filename>/etc/machine-id</filename> on mounted (but not