If CONFIG_FEATURE_INDIVIDUAL is enabled for busybox, yocto-based systems cannot start correctly. We use update-alternatives to create the symlinks and currently the ALTERNATIVE_TARGET defaults to "/bin/busybox". If we build busybox as individual apps, "/bin/busybox" doesn't exist. So when system starts, commands like 'mount' cannot be found, causing a system halt. //Chen Qi
What is the effect change in disk space, or are they all still symlinks just not to busybox binary?
Hi Saul, If busybox is built as a single binary, on our system, we'll have links like below. /bin/ls -> /bin/busybox /bin/cat -> /bin/busybox .... If busybox is built as individual apps, on our system, we'll have links like below. /bin/ls -> /bin/ls.busybox /bin/cat -> /bin/cat.busybox .... If busybox is built as individual apps, the rootfs size is about 1M larger. After all, those apps are not compressed into one binary.
merged into poky/master: 9d68aa5e3590c8eefb221f62b0390a05061a756a http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=87efa83191f0b4f4cec3a821b6dfe425c781c077