13.08.2011 08:23, auto38092...@hushmail.com пишет: > I wrote: > >> I wish I didn't feel the need to mention this, but >> on a related note, I am worried that "apt-get dist-upgrade" >> (or maybe it was "aptitude full-upgrade") failed to >> upgrade busybox. > > It turns out that "apt-get dist-upgrade" didn't complete. > > I suspect that's why busybox wasn't upgraded.
1.1.3 busybox is quite old, and I'm afraid to dig that deep, especially having in mind that you jumped over several debian versions while upgrading. Can we perhaps close this bug now when you solved the issue? There was an attempt at one point to get rid (correctly!) of CONFIG_PREFER_APPLETS busybox configuration setting -- where busybox searches for a command in a list of its applets first and goes to $PATH next if that fails. That version was one of these, so you actually need the symlinks such as sh, mount, umount etc to point to busybox binary. That version is incompatible with current initramfs-tools, because mkinitramfs does not create these symlinks. So I think it'd be a good idea to add Conflicts: busybox (<<version) to initramfs-tools package in order to prevent such situation in the future. I think it was enabled again in 1.10.2-2. /mjt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e4903d3.9000...@msgid.tls.msk.ru
