Unfortunately that's difficult; I tried to arrange for it in the past
and it caused problems due to exactly where busybox-initramfs sits in
the dependency graph. It shouldn't be a problem for upgrades from Feisty
to Gutsy, and it should sort itself out naturally as other packages get
uploaded.
--
Have you used update-initramfs to rebuild the ramdisks once the new
busybox was installed?
--
Segfaults during boot (from mount)
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Confirmed fixed here. :)
--
Segfaults during boot (from mount)
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Fixed here, too. Though automatically causing update-initramfs to run
would have been nice.
--
Segfaults during boot (from mount)
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Fixed after using update-initramfs, but I think the update package
procedure should have done that (or at least explicitly tell me what to
do to complete the update), since I've never manually installed this
package. Please consider this for future updates.
--
Segfaults during boot (from mount)
The busybox fix works here.
--
Segfaults during boot (from mount)
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've updated to busybox-initramfs package version 1:1.1.3-5ubuntu4, but
I still see the 3 Segmentation fault messages in VT1.
--
Segfaults during boot (from mount)
https://bugs.launchpad.net/bugs/131961
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
