Bug 4570

Summary:	busybox in Yocto/OE doesn't support FEATURE_INDIVIDUAL
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Chen Qi <Qi.Chen>
Component:	core	Assignee:	Chen Qi <Qi.Chen>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	liezhi.yang, mark.hatle, meta.mr.watcher, meta.watcher, sgw, yi.zhao
Version:	1.4
Target Milestone:	1.1.2
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---
Bug Depends on:
Bug Blocks:	4207

Description Chen Qi 2013-05-29 09:13:35 UTC

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

Comment 1 Saul Wold 2013-05-30 07:40:57 UTC

What is the effect change in disk space, or are they all still symlinks just not to busybox binary?

Comment 2 Chen Qi 2013-05-30 07:51:18 UTC

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.

Comment 3 Chen Qi 2013-06-26 03:12:40 UTC

merged into poky/master: 9d68aa5e3590c8eefb221f62b0390a05061a756a

http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=87efa83191f0b4f4cec3a821b6dfe425c781c077