diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-09-15 13:43:59 +0100 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-09-20 16:48:50 +0200 |
| commit | b66a6e1a5838b874b789820c090dd6850cf10513 (patch) | |
| tree | df30d43665c3bd1e29d6efe294c2c9e5e237dfd0 /man/bootup.xml | |
| parent | 483bf5643aa1bdb498d7055ea20f534eac1d1486 (diff) | |
| download | systemd-b66a6e1a5838b874b789820c090dd6850cf10513.tar.gz | |
man: "the initial RAM disk" → "the initrd"
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 <filename></filename> and other minor cleanups.
Diffstat (limited to 'man/bootup.xml')
| -rw-r--r-- | man/bootup.xml | 14 |
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 |