diff options
| author | Scott Rifenbark <srifenbark@gmail.com> | 2019-05-06 12:44:48 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-05-07 10:23:42 +0100 |
| commit | 59f95aaae45e3b9f6c6a2d3f2acc387ea49add07 (patch) | |
| tree | 5d5525a1d6489f0ba806d21c5ab316b839e4232f /documentation/ref-manual/ref-kickstart.xml | |
| parent | 2a540a95a52e5b750d708f7531acf759c8630763 (diff) | |
| download | poky-59f95aaae45e3b9f6c6a2d3f2acc387ea49add07.tar.gz | |
documentation: Cleaned up "plug-in"/"plugin" terminology.
The YP manual set was using the plugin term inconsistently.
It was appearing as "plugin" as well as "plug-in". The
plugins in the project are all named without a hyphen.
The term itself is either/or according to Google. I have
changed all references to plugin so that they do not use
a hyphen.
(From yocto-docs rev: 715bb58e2347c5e37a49da7d9e3e230503672337)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/ref-kickstart.xml')
| -rw-r--r-- | documentation/ref-manual/ref-kickstart.xml | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/documentation/ref-manual/ref-kickstart.xml b/documentation/ref-manual/ref-kickstart.xml index a58f9d7c96..1128bd50d0 100644 --- a/documentation/ref-manual/ref-kickstart.xml +++ b/documentation/ref-manual/ref-kickstart.xml | |||
| @@ -117,9 +117,9 @@ | |||
| 117 | This option is a Wic-specific option that names the source | 117 | This option is a Wic-specific option that names the source |
| 118 | of the data that populates the partition. | 118 | of the data that populates the partition. |
| 119 | The most common value for this option is "rootfs", but you | 119 | The most common value for this option is "rootfs", but you |
| 120 | can use any value that maps to a valid source plug-in. | 120 | can use any value that maps to a valid source plugin. |
| 121 | For information on the source plug-ins, see the | 121 | For information on the source plugins, see the |
| 122 | "<ulink url='&YOCTO_DOCS_DEV_URL;#wic-using-the-wic-plug-ins-interface'>Using the Wic Plug-Ins Interface</ulink>" | 122 | "<ulink url='&YOCTO_DOCS_DEV_URL;#wic-using-the-wic-plugin-interface'>Using the Wic Plugins Interface</ulink>" |
| 123 | section in the Yocto Project Development Tasks Manual. | 123 | section in the Yocto Project Development Tasks Manual. |
| 124 | </para> | 124 | </para> |
| 125 | 125 | ||
| @@ -139,12 +139,12 @@ | |||
| 139 | <filename>--source <replaceable>plugin-name</replaceable></filename>, | 139 | <filename>--source <replaceable>plugin-name</replaceable></filename>, |
| 140 | Wic creates a partition as large as needed and fills it | 140 | Wic creates a partition as large as needed and fills it |
| 141 | with the contents of the partition that is generated by the | 141 | with the contents of the partition that is generated by the |
| 142 | specified plug-in name using the data pointed to by the | 142 | specified plugin name using the data pointed to by the |
| 143 | <filename>-r</filename> command-line option or the | 143 | <filename>-r</filename> command-line option or the |
| 144 | equivalent rootfs derived from the <filename>-e</filename> | 144 | equivalent rootfs derived from the <filename>-e</filename> |
| 145 | command-line option. | 145 | command-line option. |
| 146 | Exactly what those contents are and filesystem type used are | 146 | Exactly what those contents are and filesystem type used are |
| 147 | dependent on the given plug-in implementation. | 147 | dependent on the given plugin implementation. |
| 148 | </para> | 148 | </para> |
| 149 | 149 | ||
| 150 | <para>If you do not use the <filename>--source</filename> | 150 | <para>If you do not use the <filename>--source</filename> |
| @@ -220,7 +220,7 @@ | |||
| 220 | This option is a Wic-specific option that excludes the given | 220 | This option is a Wic-specific option that excludes the given |
| 221 | relative path from the resulting image. | 221 | relative path from the resulting image. |
| 222 | This option is only effective with the rootfs source | 222 | This option is only effective with the rootfs source |
| 223 | plug-in. | 223 | plugin. |
| 224 | </para></listitem> | 224 | </para></listitem> |
| 225 | <listitem><para> | 225 | <listitem><para> |
| 226 | <emphasis><filename>--extra-space</filename>:</emphasis> | 226 | <emphasis><filename>--extra-space</filename>:</emphasis> |
| @@ -299,7 +299,7 @@ | |||
| 299 | supports the following options: | 299 | supports the following options: |
| 300 | <note> | 300 | <note> |
| 301 | Bootloader functionality and boot partitions are implemented by | 301 | Bootloader functionality and boot partitions are implemented by |
| 302 | the various <filename>--source</filename> plug-ins that | 302 | the various <filename>--source</filename> plugins that |
| 303 | implement bootloader functionality. | 303 | implement bootloader functionality. |
| 304 | The bootloader command essentially provides a means of | 304 | The bootloader command essentially provides a means of |
| 305 | modifying bootloader configuration. | 305 | modifying bootloader configuration. |
