From b66a6e1a5838b874b789820c090dd6850cf10513 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Thu, 15 Sep 2022 13:43:59 +0100 Subject: =?UTF-8?q?man:=20"the=20initial=20RAM=20disk"=20=E2=86=92=20"the?= =?UTF-8?q?=20initrd"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit In many places we spelled out the phrase behind "initrd" in full, but this isn't terribly useful. In fact, no "RAM disk" is used, so emphasizing this is just confusing to the reader. Let's just say "initrd" everywhere, people understand what this refers to, and that it's in fact an initramfs image. Also, s/i.e./e.g./ where appropriate. Also, don't say "in RAM", when in fact it's virtual memory, whose pages may or may not be loaded in page frames in RAM, and we have no control over this. Also, add and other minor cleanups. --- man/systemd-boot.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'man/systemd-boot.xml') diff --git a/man/systemd-boot.xml b/man/systemd-boot.xml index 7a2d3ec826..0eee532f90 100644 --- a/man/systemd-boot.xml +++ b/man/systemd-boot.xml @@ -444,7 +444,7 @@ stored in the EFI variable LoaderSystemToken (see below). During early OS boot the system manager reads this variable and passes it to the OS kernel's random pool, crediting the full entropy it contains. This is an efficient way to ensure the system starts up with a fully initialized - kernel random pool — as early as the initial RAM disk phase. systemd-boot reads + kernel random pool — as early as the initrd phase. systemd-boot reads the random seed from the ESP, combines it with the "system token", and both derives a new random seed to update in-place the seed stored in the ESP, and the random seed to pass to the OS from it via SHA256 hashing in counter mode. This ensures that different physical systems that boot the same -- cgit v1.2.1