From 9cef06f6931b7cd7589d38a3eb7dfc3732d5993f Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 17 Sep 2013 07:46:36 -0700 Subject: [PATCH] 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 Signed-off-by: Richard Purdie --- documentation/ref-manual/closer-look.xml | 27 +++++++++++++++++------- 1 file changed, 19 insertions(+), 8 deletions(-) diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index 9ce92af910..f3f0db2dd6 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml @@ -921,12 +921,23 @@ - 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. + + + + 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 + read-only root filesystem, + all the post installation scripts must succeed during the + package installation phase since the root filesystem cannot be written into. @@ -935,10 +946,10 @@ the image. These processes include mklibs and prelink. - The mklibs optimizes the size of the - libraries. + The mklibs process optimizes the size + of the libraries. A prelink 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.