4570 2013-05-29 09:13:35 +0000 busybox in Yocto/OE doesn't support FEATURE_INDIVIDUAL 2013-06-26 03:12:40 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.4 x86 Multiple RESOLVED FIXED Medium normal 1.1.2 4207 1 Qi.Chen Qi.Chen liezhi.yang mark.hatle meta.mr.watcher meta.watcher sgw yi.zhao --- --- --- oldest_to_newest 33356 0 Qi.Chen 2013-05-29 09:13:35 +0000 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 33386 1 sgw 2013-05-30 07:40:57 +0000 What is the effect change in disk space, or are they all still symlinks just not to busybox binary? 33387 2 Qi.Chen 2013-05-30 07:51:18 +0000 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. 34147 3 Qi.Chen 2013-06-26 03:12:40 +0000 merged into poky/master: 9d68aa5e3590c8eefb221f62b0390a05061a756a http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=87efa83191f0b4f4cec3a821b6dfe425c781c077