sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

ref-manual: Update to the image generation section. 

Fixes [YOCTO #2808]

Applied some Eggleton review edits to the image generation section.
Minor tweaks and a cross-reference to the read-only root
filesystem section in the dev-manual.

(From yocto-docs rev: e41a08872e398d10c452bb5e1f1e6af41a525ab2)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-09-17 07:46:36 -07:00 committed by Richard Purdie
parent 5cdf8a6363
commit 9cef06f693
1 changed files with 19 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
documentation/ref-manual/closer-look.xml
View File

@ -921,12 +921,23 @@
</para>
<para>
The process runs all of the post installation scripts, and
any that fail to run on the build host will be run on the
Package installation is under control of the package manager
(e.g. smart/rpm, opkg, or apt/dpkg) regardless of whether or
not package management is enabled for the target.
At the end of the process, if package management is not
enabled for the target, the package manager's data files
are deleted from the root filesystem.
</para>
<para>
During image generation, the build system attempts to run
all post installation scripts.
Any that fail to run on the build host are run on the
target when the target system is first booted.
If you are using a read-only root filesystem, all the post
installation scripts must succeed during the package
installation phase since the root filesystem cannot be
If you are using a
<ulink url='&YOCTO_DOCS_DEV_URL;#creating-a-read-only-root-filesystem'>read-only root filesystem</ulink>,
all the post installation scripts must succeed during the
package installation phase since the root filesystem cannot be
written into.
</para>
@ -935,10 +946,10 @@
the image.
These processes include <filename>mklibs</filename> and
<filename>prelink</filename>.
The <filename>mklibs</filename> optimizes the size of the
libraries.
The <filename>mklibs</filename> process optimizes the size
of the libraries.
A <filename>prelink</filename> process optimizes the dynamic
linking of shared libraries to reduce start up time of the
linking of shared libraries to reduce start up time of
executables.
</para>