diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2024-03-30 18:56:12 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2024-04-12 17:29:34 +0100 |
commit | a738448d83e28e97501ac30076f980efeeab4c83 (patch) | |
tree | 2a3c2b59913923d0734b4b72cbb6155c920f6236 /documentation/ref-manual | |
parent | 3ad2f245f0780bab65f01bca8b813bae9b06ca76 (diff) | |
download | poky-a738448d83e28e97501ac30076f980efeeab4c83.tar.gz |
manuals: remove tab characters
As reported by "make sphinx-lint"
Tabs are even removed in Makefile examples,
as Sphinx turns them to spaces anyway in the generated output.
(From yocto-docs rev: 20e9c0c9fad3109567948af6bc40bb0fa2a5552b)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r-- | documentation/ref-manual/terms.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/ref-manual/terms.rst b/documentation/ref-manual/terms.rst index ad9c46c339..b18c4183b6 100644 --- a/documentation/ref-manual/terms.rst +++ b/documentation/ref-manual/terms.rst | |||
@@ -228,23 +228,23 @@ universal, the list includes them just in case: | |||
228 | 228 | ||
229 | As far as bootloaders are concerned, :term:`Initramfs` and "initrd" | 229 | As far as bootloaders are concerned, :term:`Initramfs` and "initrd" |
230 | images are still copied to RAM in the same way. That's why most | 230 | images are still copied to RAM in the same way. That's why most |
231 | most bootloaders refer to :term:`Initramfs` images as "initrd" | 231 | most bootloaders refer to :term:`Initramfs` images as "initrd" |
232 | or "init RAM disk". | 232 | or "init RAM disk". |
233 | 233 | ||
234 | This kind of mechanism is typically used for two reasons: | 234 | This kind of mechanism is typically used for two reasons: |
235 | 235 | ||
236 | - For booting the same kernel binary on multiple systems requiring | 236 | - For booting the same kernel binary on multiple systems requiring |
237 | different device drivers. The :term:`Initramfs` image is then customized | 237 | different device drivers. The :term:`Initramfs` image is then customized |
238 | for each type of system, to include the specific kernel modules | 238 | for each type of system, to include the specific kernel modules |
239 | necessary to access the final root filesystem. This technique | 239 | necessary to access the final root filesystem. This technique |
240 | is used on all GNU / Linux distributions for desktops and servers. | 240 | is used on all GNU / Linux distributions for desktops and servers. |
241 | 241 | ||
242 | - For booting faster. As the root filesystem is extracted into RAM, | 242 | - For booting faster. As the root filesystem is extracted into RAM, |
243 | accessing the first user-space applications is very fast, compared | 243 | accessing the first user-space applications is very fast, compared |
244 | to having to initialize a block device, to access multiple blocks | 244 | to having to initialize a block device, to access multiple blocks |
245 | from it, and to go through a filesystem having its own overhead. | 245 | from it, and to go through a filesystem having its own overhead. |
246 | For example, this allows to display a splashscreen very early, | 246 | For example, this allows to display a splashscreen very early, |
247 | and to later take care of mounting the final root filesystem and | 247 | and to later take care of mounting the final root filesystem and |
248 | loading less time-critical kernel drivers. | 248 | loading less time-critical kernel drivers. |
249 | 249 | ||
250 | This cpio archive can either be loaded to RAM by the bootloader, | 250 | This cpio archive can either be loaded to RAM by the bootloader, |