On Tue, 2016-06-07 at 13:07 +0200, Bastian Blank wrote: > On Tue, Jun 07, 2016 at 11:39:25AM +0100, Ben Hutchings wrote: > > > This only happens when there is a config file that sets > > > BUSYBOX=y. You > > > can find that config file with: > > > > > > grep -r BUSYBOX=y /etc/initramfs-tools/initramfs-tools.conf \ > > > /usr/share/initramfs-tools/conf-hooks.d > > > > > > If it's the one in /etc, that's user error, otherwise it's a bug > > > in whichever package owns the file. > > Well, which is it? > > $ grep BUSYBOX= /etc/initramfs-tools/initramfs.conf > BUSYBOX=y > > /etc/initramfs-tools/initramfs.conf is not a conf-file, according to > dpkg, so it needs to be updated by other means. Sure it is. $ dpkg -S /etc/initramfs-tools/initramfs.conf initramfs-tools-core: /etc/initramfs-tools/initramfs.conf The old default of BUSYBOX=y (which then meant 'use busybox if available') was changed to BUSYBOX=auto on upgrade to version 0.121. But it's possible that this isn't always handled properly because an upgrade to 0.121 or later also moves this conffile from initramfs-tools to initramfs-tools-core. That was also reported in #822671, for which I still need to review the patch. Is this perhaps the same bug? Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson
Attachment:
signature.asc
Description: This is a digitally signed message part