summaryrefslogtreecommitdiff
path: root/man/bootup.xml
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2022-09-23 14:59:02 +0200
committerLennart Poettering <lennart@poettering.net>2022-09-23 15:10:53 +0200
commit32e276708089110243682d8aaa3d58075b91f0d6 (patch)
tree44a32b969266f7dfe9529f31e79046e78ca7e474 /man/bootup.xml
parentaddc84ec9184094db4439006e8a3b955b6387f74 (diff)
downloadsystemd-32e276708089110243682d8aaa3d58075b91f0d6.tar.gz
tree-wide: use the term "initrd" at most places we so far used "initramfs"
In most cases we refernced the concept as "initrd". Let's convert most remaining uses of "initramfs" to "initrd" too, to stay internally consistent. This leaves "initramfs" only where it's relevant to explain historical concepts or where "initramfs" is part of the API (i.e. in /run/initramfs). Follow-up for: b66a6e1a5838b874b789820c090dd6850cf10513
Diffstat (limited to 'man/bootup.xml')
-rw-r--r--man/bootup.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/man/bootup.xml b/man/bootup.xml
index 62a34fe3d7..16bb9c0b3f 100644
--- a/man/bootup.xml
+++ b/man/bootup.xml
@@ -31,9 +31,9 @@
boot loader will then invoke an OS kernel from disk (or the network). On systems using EFI or other types
of firmware, this firmware may also load the kernel directly.</para>
- <para>The kernel (optionally) mounts an in-memory file system, often generated by
- <citerefentry project='man-pages'><refentrytitle>dracut</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
- which looks for the root file system. Nowadays this is implemented as an "initramfs" — a compressed CPIO
+ <para>The kernel (optionally) mounts an in-memory file system, often generated by <citerefentry
+ project='man-pages'><refentrytitle>dracut</refentrytitle><manvolnum>8</manvolnum></citerefentry>, which
+ looks for the root file system. Nowadays this is implemented as an "initramfs" — a compressed CPIO
archive that the kernel extracts into a tmpfs. In the past normal file systems using an in-memory block
device (ramdisk) were used, and the name "initrd" is still used to describe both concepts. It's the boot
loader or the firmware that loads both the kernel and initrd/initramfs images into memory, but the kernel