From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-core@lists.openembedded.org
Subject: busybox can no longer upgrade on a running system
Date: Sun, 10 Jan 2016 19:29:40 +0100 [thread overview]
Message-ID: <5692A314.9030808@topic.nl> (raw)
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
reply other threads:[~2016-01-10 18:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5692A314.9030808@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.