From 8f39ecf6aa5bdfd2498e147476eb4b8f25d817bc Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Wed, 23 Mar 2022 12:04:28 +0100 Subject: docs: link up new image building docs a bit --- man/machine-id.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'man/machine-id.xml') diff --git a/man/machine-id.xml b/man/machine-id.xml index d5d3a1a299..9bd49582fc 100644 --- a/man/machine-id.xml +++ b/man/machine-id.xml @@ -80,13 +80,13 @@ /etc/machine-id may also be written using any other means. - For operating system images which are created once and used on multiple - machines, for example for containers or in the cloud, - /etc/machine-id 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. + For operating system images which are created once and used on multiple machines, for example for + containers or in the cloud, /etc/machine-id 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 Safely + Building Images. systemd-firstboot1 may be used to initialize /etc/machine-id on mounted (but not -- cgit v1.2.1