* busybox can no longer upgrade on a running system
@ 2016-01-10 18:29 Mike Looijmans
0 siblings, 0 replies; only message in thread
From: Mike Looijmans @ 2016-01-10 18:29 UTC (permalink / raw)
To: openembedded-core
Don't think anyone noticed yet, but if you try to upgrade busybox
through "opkg upgrade", you'll end up with a bricked box.
Apparently busybox kills the /bin/sh link somewhere during the upgrade,
and that results in the upgrade failing and a system that won't boot.
One way to work around the problem appears to be to remove "/bin/sh"
from the busybox.links.nosuid file, so that update-alternatives won't
touch it.
I haven't figured out yet what caused the regression. It's probably been
like this for months.
--
Mike Looijmans
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-01-10 18:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-10 18:29 busybox can no longer upgrade on a running system Mike Looijmans
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.