<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 07/01/2013 03:33 PM, Martin Jansa
wrote:<br>
</div>
<blockquote
cite="mid:CA+chaQcMRE9HZ_pv4YLKEjvYfa2HBFTYL+Tvg6CAWSWnULtRMQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi Chen,
<div><br>
</div>
<div>1) install image created before this change on target
device (which doesn't include coreutils, wget and is depending
on usable busybox)</div>
<div>2) build feeds which include this change</div>
<div>3) run "opkg update && opkg upgrade" on target
device (or equivalent in your favorite package manager)</div>
<div>4) you'll get unusable (and probably unbootable) system at
this point, because /bin/busybox binary from old busybox
version was already removed, but u-a symlinks to new
/bin/busybox.(no)suid weren't created because "sed" used in
u-a doesn't work anymore.</div>
<div><br>
</div>
<div>As work around I've used</div>
<div>ln -s /bin/busybox.nosuid /bin/busybox</div>
<div>to make old u-a links happy and able to finish postinst in
new busybox version.</div>
<div><br>
</div>
<div>FWIW: having /bin/busybox -> busybox.nosuid sounds like
good idea to have "default" busybox in path for people who're
running it directly.</div>
<div><br>
</div>
<div>Regards,</div>
</div>
<div class="gmail_extra"><br>
</div>
</blockquote>
Hi Martin,<br>
<br>
I forgot the on device upgrade issue when I made the patchset. <br>
Thank you for pointing it out.<br>
<br>
I did some tests. The on device upgrade did broke with opkg as the
package manager. RPM does not have this problem.<br>
<br>
I'll make a follow-up patch to fix this problem tomorrow.<br>
<br>
Thanks a lot,<br>
Chen Qi<br>
<br>
<br>
<br>
</body>
</html>