diff options
Diffstat (limited to 'documentation/ref-manual/features.rst')
-rw-r--r-- | documentation/ref-manual/features.rst | 37 |
1 files changed, 16 insertions, 21 deletions
diff --git a/documentation/ref-manual/features.rst b/documentation/ref-manual/features.rst index 2ea946b31d..2c074ab9c7 100644 --- a/documentation/ref-manual/features.rst +++ b/documentation/ref-manual/features.rst | |||
@@ -12,7 +12,7 @@ Features provide a mechanism for working out which packages should be | |||
12 | included in the generated images. Distributions can select which | 12 | included in the generated images. Distributions can select which |
13 | features they want to support through the :term:`DISTRO_FEATURES` variable, | 13 | features they want to support through the :term:`DISTRO_FEATURES` variable, |
14 | which is set or appended to in a distribution's configuration file such | 14 | which is set or appended to in a distribution's configuration file such |
15 | as ``poky.conf``, ``poky-tiny.conf``, ``poky-lsb.conf`` and so forth. | 15 | as ``poky.conf``, ``poky-tiny.conf``, ``poky-altcfg.conf`` and so forth. |
16 | Machine features are set in the :term:`MACHINE_FEATURES` variable, which is | 16 | Machine features are set in the :term:`MACHINE_FEATURES` variable, which is |
17 | set in the machine configuration file and specifies the hardware | 17 | set in the machine configuration file and specifies the hardware |
18 | features for a given machine. | 18 | features for a given machine. |
@@ -146,7 +146,7 @@ metadata, as extra layers can define their own: | |||
146 | 146 | ||
147 | - *directfb:* Include DirectFB support. | 147 | - *directfb:* Include DirectFB support. |
148 | 148 | ||
149 | - *ext2:* Include tools for supporting for devices with internal | 149 | - *ext2:* Include tools for supporting devices with internal |
150 | HDD/Microdrive for storing files (instead of Flash only devices). | 150 | HDD/Microdrive for storing files (instead of Flash only devices). |
151 | 151 | ||
152 | - *gobject-introspection-data:* Include data to support | 152 | - *gobject-introspection-data:* Include data to support |
@@ -167,9 +167,6 @@ metadata, as extra layers can define their own: | |||
167 | - *multiarch:* Enable building applications with multiple architecture | 167 | - *multiarch:* Enable building applications with multiple architecture |
168 | support. | 168 | support. |
169 | 169 | ||
170 | - *ld-is-gold:* Use the :wikipedia:`gold <Gold_(linker)>` | ||
171 | linker instead of the standard GCC linker (bfd). | ||
172 | |||
173 | - *ldconfig:* Include support for ldconfig and ``ld.so.conf`` on the | 170 | - *ldconfig:* Include support for ldconfig and ``ld.so.conf`` on the |
174 | target. | 171 | target. |
175 | 172 | ||
@@ -197,13 +194,17 @@ metadata, as extra layers can define their own: | |||
197 | 194 | ||
198 | - *pcmcia:* Include PCMCIA/CompactFlash support. | 195 | - *pcmcia:* Include PCMCIA/CompactFlash support. |
199 | 196 | ||
197 | - *pni-names:* Enable generation of persistent network interface names, i.e. | ||
198 | the system tries hard to have the same but unique names for the network | ||
199 | interfaces even after a reinstall. | ||
200 | |||
200 | - *polkit:* Include :wikipedia:`Polkit <Polkit>` support. | 201 | - *polkit:* Include :wikipedia:`Polkit <Polkit>` support. |
201 | 202 | ||
202 | - *ppp:* Include PPP dialup support. | 203 | - *ppp:* Include PPP dialup support. |
203 | 204 | ||
204 | - *ptest:* Enables building the package tests where supported by | 205 | - *ptest:* Enables building the package tests where supported by |
205 | individual recipes. For more information on package tests, see the | 206 | individual recipes. For more information on package tests, see the |
206 | ":ref:`dev-manual/packages:testing packages with ptest`" section | 207 | ":ref:`test-manual/ptest:testing packages with ptest`" section |
207 | in the Yocto Project Development Tasks Manual. | 208 | in the Yocto Project Development Tasks Manual. |
208 | 209 | ||
209 | - *pulseaudio:* Include support for | 210 | - *pulseaudio:* Include support for |
@@ -281,31 +282,24 @@ The image features available for all images are: | |||
281 | - *dbg-pkgs:* Installs debug symbol packages for all packages installed | 282 | - *dbg-pkgs:* Installs debug symbol packages for all packages installed |
282 | in a given image. | 283 | in a given image. |
283 | 284 | ||
284 | - *debug-tweaks:* Makes an image suitable for development (e.g. allows | ||
285 | root logins, logins without passwords ---including root ones, and enables | ||
286 | post-installation logging). See the ``allow-empty-password``, | ||
287 | ``allow-root-login``, ``empty-root-password``, and ``post-install-logging`` | ||
288 | features in this list for additional information. | ||
289 | |||
290 | - *dev-pkgs:* Installs development packages (headers and extra library | 285 | - *dev-pkgs:* Installs development packages (headers and extra library |
291 | links) for all packages installed in a given image. | 286 | links) for all packages installed in a given image. |
292 | 287 | ||
293 | - *doc-pkgs:* Installs documentation packages for all packages | 288 | - *doc-pkgs:* Installs documentation packages for all packages |
294 | installed in a given image. | 289 | installed in a given image. |
295 | 290 | ||
296 | - *empty-root-password:* This feature or ``debug-tweaks`` is required if | 291 | - *empty-root-password:* This feature can be used if you want to allow root |
297 | you want to allow root login with an empty password. If these features | 292 | login with an empty password. If this feature is not present in |
298 | are not present in :term:`IMAGE_FEATURES`, a non-empty password is | 293 | :term:`IMAGE_FEATURES`, a non-empty password is forced in ``/etc/passwd`` and |
299 | forced in ``/etc/passwd`` and ``/etc/shadow`` if such files exist. | 294 | ``/etc/shadow`` if such files exist. |
300 | 295 | ||
301 | .. note:: | 296 | .. note:: |
302 | ``empty-root-password`` doesn't set an empty root password by itself. | 297 | ``empty-root-password`` doesn't set an empty root password by itself. |
303 | You get an initial empty root password thanks to the | 298 | You get an initial empty root password thanks to the |
304 | :oe_git:`base-passwd </openembedded-core/tree/meta/recipes-core/base-passwd/>` | 299 | :oe_git:`base-passwd </openembedded-core/tree/meta/recipes-core/base-passwd/>` |
305 | and :oe_git:`shadow </openembedded-core/tree/meta/recipes-extended/shadow/>` | 300 | and :oe_git:`shadow </openembedded-core/tree/meta/recipes-extended/shadow/>` |
306 | recipes, and the presence of ``empty-root-password`` or ``debug-tweaks`` | 301 | recipes, and the presence of ``empty-root-password`` just disables the |
307 | just disables the mechanism which forces an non-empty password for the | 302 | mechanism which forces an non-empty password for the root user. |
308 | root user. | ||
309 | 303 | ||
310 | - *lic-pkgs:* Installs license packages for all packages installed in a | 304 | - *lic-pkgs:* Installs license packages for all packages installed in a |
311 | given image. | 305 | given image. |
@@ -323,8 +317,9 @@ The image features available for all images are: | |||
323 | 317 | ||
324 | .. note:: | 318 | .. note:: |
325 | 319 | ||
326 | To make the ``/var/log`` directory on the target persistent, use the | 320 | To make the ``/var/log`` directory on the target persistent, remove the |
327 | :term:`VOLATILE_LOG_DIR` variable by setting it to "no". | 321 | ``files/fs-perms-volatile-log.txt`` value from |
322 | :term:`FILESYSTEM_PERMS_TABLES`. | ||
328 | 323 | ||
329 | - *ptest-pkgs:* Installs ptest packages for all ptest-enabled recipes. | 324 | - *ptest-pkgs:* Installs ptest packages for all ptest-enabled recipes. |
330 | 325 | ||