summaryrefslogtreecommitdiff
path: root/man/bootup.xml
diff options
context:
space:
mode:
Diffstat (limited to 'man/bootup.xml')
-rw-r--r--man/bootup.xml14
1 files changed, 7 insertions, 7 deletions
diff --git a/man/bootup.xml b/man/bootup.xml
index 6c69c8a9bd..62a34fe3d7 100644
--- a/man/bootup.xml
+++ b/man/bootup.xml
@@ -33,13 +33,13 @@
<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 usually implemented as an initramfs — a compressed
- archive which is extracted when the kernel boots up into a lightweight in-memory file system based on
- tmpfs, but 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 which interprets it as a file
- system. <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry> may
- be used to manage services in the initrd, similarly to the real system.</para>
+ 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
+ which interprets it as a file system.
+ <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry> may be used
+ to manage services in the initrd, similarly to the real system.</para>
<para>After the root file system is found and mounted, the initrd hands over control to the host's system
manager (such as