[YOCTO #936] "update-alternatives" installed: one in /usr/sbin from chkconfig \ (symlinked to "alternatives"), and the other in /usr/bin \ from update-alternatives-cworth. It appears for whatever reason that the one from chkconfig is run \ during postinst processing but if you run the script from the command \ line it gets the other one. this is due to differences in the PATH environment variable. The following is the sequence to call scripts after kernel booting inittab -->rcS -->./S40networking(PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin) -->S98configure(call rpm-postinstall) #"/usr/sbin" is found prior to "/usr/bin", so update-alternatives from chkconfig is run in this script -->rc5.d -->profile(profile:4:PATH="/usr/local/bin:/usr/bin:/bin" profile:15: PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin) #"/usr/bin/" is found prior to "/usr/sbin", so update-alternatives from update-alternatives-cworth is run in this script So I remove the symlink (update-alternatives linked to chkconfig). The one from update-alternatives-cworth is left alone. (From OE-Core rev: f3a52a73251b26ead15abd4910dc82c1011ab852) Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |
||
---|---|---|
bitbake | ||
documentation | ||
meta | ||
meta-demoapps | ||
meta-rt | ||
meta-skeleton | ||
meta-yocto | ||
scripts | ||
.gitignore | ||
LICENSE | ||
README | ||
README.hardware | ||
oe-init-build-env |
README
Poky ==== Poky is an integration of various components to form a complete prepackaged build system and development environment. It features support for building customised embedded device style images. There are reference demo images featuring a X11/Matchbox/GTK themed UI called Sato. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK with IDE integration. Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of layers which extend the systems capabilities in a modular way. As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information e.g. for the hardware support. Poky is in turn a component of the Yocto Project. The Yocto Project has extensive documentation about the system including a reference manual which can be found at: http://yoctoproject.org/community/documentation For information about OpenEmbedded see their website: http://www.openembedded.org/