4802 2013-07-02 10:48:23 +0000 Busybox on target upgrade fails if upgrading from 'one-binary' version to 'two-binary' version 2013-07-09 03:03:53 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.4 x86 Multiple RESOLVED FIXED Undecided normal 1.5 M2 1 Qi.Chen Qi.Chen liezhi.yang mark.hatle Martin.Jansa meta.mr.watcher meta.watcher sgw yi.zhao --- --- --- oldest_to_newest 34277 0 Qi.Chen 2013-07-02 10:48:23 +0000 First of all, thanks Martin for pointing it out. We've made busybox default to two binaries, busybox.nosuid and busybox.suid. We also add a variable 'BUSYBOX_SPLIT_SUID‘ to control its behavior. Now that we can have a busybox version with only one binary (/bin/busybox) or we can have a version with two binaries (/bin/busybox.nosuid and /bin/busybox.suid), the on-device upgrade issue starts to become a problem. We have to support four upgrade paths: A: busybox[split] B: busybox[no split] A --(upgrade)--> B B --(upgrade)--> A A --(upgrade)--> A B --(upgrade)--> B This problem can be more complex if we take into consideration the upgrade issue of other related packages, for example, busybox-syslog. The goal here is to make any upgrade path above successful. //Chen Qi 34405 1 Qi.Chen 2013-07-09 03:03:31 +0000 merged into poky/master: cb534214286cb59f1ac377b6f1643c923c1289b1 http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=4e571e97750f3ac6a62cd0d2d10c08be98230630