diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2021-12-16 08:22:42 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-01-07 11:12:06 +0000 |
commit | 36d200ab0adbf76d6d8197551b3304afcf069716 (patch) | |
tree | de9c18b1ea455ac2eeb4ea0a5716a9dfd5158b42 /documentation/ref-manual | |
parent | 620ba2535c0123958ec5cad56a667588cb8112f2 (diff) | |
download | poky-36d200ab0adbf76d6d8197551b3304afcf069716.tar.gz |
manuals: replace "rootfs" by "root filesystem"
Almost everyone understands "rootfs", but "root filesystem"
is real English.
(From yocto-docs rev: 3d610f15e5b6be3435e9e81e4498a676671e5b39)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r-- | documentation/ref-manual/classes.rst | 10 | ||||
-rw-r--r-- | documentation/ref-manual/kickstart.rst | 4 | ||||
-rw-r--r-- | documentation/ref-manual/variables.rst | 2 |
3 files changed, 8 insertions, 8 deletions
diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst index e70c7d9013..99d9a7a3e7 100644 --- a/documentation/ref-manual/classes.rst +++ b/documentation/ref-manual/classes.rst | |||
@@ -1362,9 +1362,9 @@ is set to 0. | |||
1362 | 1362 | ||
1363 | Only a single Initramfs bundle can be added to the FIT image created by | 1363 | Only a single Initramfs bundle can be added to the FIT image created by |
1364 | ``kernel-fitimage`` and the Initramfs bundle in FIT is optional. | 1364 | ``kernel-fitimage`` and the Initramfs bundle in FIT is optional. |
1365 | In case of Initramfs, the kernel is configured to be bundled with the rootfs | 1365 | In case of Initramfs, the kernel is configured to be bundled with the root filesystem |
1366 | in the same binary (example: zImage-initramfs-:term:`MACHINE`.bin). | 1366 | in the same binary (example: zImage-initramfs-:term:`MACHINE`.bin). |
1367 | When the kernel is copied to RAM and executed, it unpacks the Initramfs rootfs. | 1367 | When the kernel is copied to RAM and executed, it unpacks the Initramfs root filesystem. |
1368 | The Initramfs bundle can be enabled when :term:`INITRAMFS_IMAGE` | 1368 | The Initramfs bundle can be enabled when :term:`INITRAMFS_IMAGE` |
1369 | is specified and that :term:`INITRAMFS_IMAGE_BUNDLE` is set to 1. | 1369 | is specified and that :term:`INITRAMFS_IMAGE_BUNDLE` is set to 1. |
1370 | The address where the Initramfs bundle is to be loaded by U-boot is specified | 1370 | The address where the Initramfs bundle is to be loaded by U-boot is specified |
@@ -1712,13 +1712,13 @@ layers. | |||
1712 | ``overlayfs.bbclass`` | 1712 | ``overlayfs.bbclass`` |
1713 | ======================= | 1713 | ======================= |
1714 | 1714 | ||
1715 | It's often desired in Embedded System design to have a read-only rootfs. | 1715 | It's often desired in Embedded System design to have a read-only root filesystem. |
1716 | But a lot of different applications might want to have read-write access to | 1716 | But a lot of different applications might want to have read-write access to |
1717 | some parts of a filesystem. It can be especially useful when your update mechanism | 1717 | some parts of a filesystem. It can be especially useful when your update mechanism |
1718 | overwrites the whole rootfs, but you may want your application data to be preserved | 1718 | overwrites the whole root filesystem, but you may want your application data to be preserved |
1719 | between updates. The :ref:`overlayfs <ref-classes-overlayfs>` class provides a way | 1719 | between updates. The :ref:`overlayfs <ref-classes-overlayfs>` class provides a way |
1720 | to achieve that by means of ``overlayfs`` and at the same time keeping the base | 1720 | to achieve that by means of ``overlayfs`` and at the same time keeping the base |
1721 | rootfs read-only. | 1721 | root filesystem read-only. |
1722 | 1722 | ||
1723 | To use this class, set a mount point for a partition ``overlayfs`` is going to use as upper | 1723 | To use this class, set a mount point for a partition ``overlayfs`` is going to use as upper |
1724 | layer in your machine configuration. The underlying file system can be anything that | 1724 | layer in your machine configuration. The underlying file system can be anything that |
diff --git a/documentation/ref-manual/kickstart.rst b/documentation/ref-manual/kickstart.rst index 807f5e052d..885c721297 100644 --- a/documentation/ref-manual/kickstart.rst +++ b/documentation/ref-manual/kickstart.rst | |||
@@ -87,7 +87,7 @@ the ``part`` and ``partition`` commands: | |||
87 | 87 | ||
88 | If you use ``--source rootfs``, Wic creates a partition as large as | 88 | If you use ``--source rootfs``, Wic creates a partition as large as |
89 | needed and fills it with the contents of the root filesystem pointed | 89 | needed and fills it with the contents of the root filesystem pointed |
90 | to by the ``-r`` command-line option or the equivalent rootfs derived | 90 | to by the ``-r`` command-line option or the equivalent root filesystem derived |
91 | from the ``-e`` command-line option. The filesystem type used to | 91 | from the ``-e`` command-line option. The filesystem type used to |
92 | create the partition is driven by the value of the ``--fstype`` | 92 | create the partition is driven by the value of the ``--fstype`` |
93 | option specified for the partition. See the entry on ``--fstype`` | 93 | option specified for the partition. See the entry on ``--fstype`` |
@@ -96,7 +96,7 @@ the ``part`` and ``partition`` commands: | |||
96 | If you use ``--source plugin-name``, Wic creates a partition as large | 96 | If you use ``--source plugin-name``, Wic creates a partition as large |
97 | as needed and fills it with the contents of the partition that is | 97 | as needed and fills it with the contents of the partition that is |
98 | generated by the specified plugin name using the data pointed to by | 98 | generated by the specified plugin name using the data pointed to by |
99 | the ``-r`` command-line option or the equivalent rootfs derived from | 99 | the ``-r`` command-line option or the equivalent root filesystem derived from |
100 | the ``-e`` command-line option. Exactly what those contents are and | 100 | the ``-e`` command-line option. Exactly what those contents are and |
101 | filesystem type used are dependent on the given plugin | 101 | filesystem type used are dependent on the given plugin |
102 | implementation. | 102 | implementation. |
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst index e5216b3f36..4f5d084e54 100644 --- a/documentation/ref-manual/variables.rst +++ b/documentation/ref-manual/variables.rst | |||
@@ -5302,7 +5302,7 @@ system and gives an overview of their function and contents. | |||
5302 | :term:`PACKAGE_WRITE_DEPS` | 5302 | :term:`PACKAGE_WRITE_DEPS` |
5303 | Specifies a list of dependencies for post-installation and | 5303 | Specifies a list of dependencies for post-installation and |
5304 | pre-installation scripts on native/cross tools. If your | 5304 | pre-installation scripts on native/cross tools. If your |
5305 | post-installation or pre-installation script can execute at rootfs | 5305 | post-installation or pre-installation script can execute at root filesystem |
5306 | creation time rather than on the target but depends on a native tool | 5306 | creation time rather than on the target but depends on a native tool |
5307 | in order to execute, you need to list the tools in | 5307 | in order to execute, you need to list the tools in |
5308 | :term:`PACKAGE_WRITE_DEPS`. | 5308 | :term:`PACKAGE_WRITE_DEPS`. |