Am 25.12.2015 um 14:46 schrieb Jonas Meurer: > Am 26.04.2015 um 01:35 schrieb Michael Biebl: >> On Sat, 25 Apr 2015 16:22:13 +0200 Michael Biebl <bi...@debian.org> wrote: >>> if the cryptsetup package is installed, it also installed a >>> initramfs-tools hook. >>> >>> I use BUSYBOX=no in initramfs.conf, but the cryptroot hook copies >>> /bin/busybox to the initramfs nonetheless. >>> >>> As a result, the initramfs is unable to boot the system >> >> I looked into this in more detail, and the culprit seems to be >> /usr/share/initramfs-tools/conf-hooks.d/cryptsetup >> which forcefully set's >> BUSYBOX=y. > > Yes, cryptsetup initramfs scripts do depend on busybox. At least this > was the case some years ago. > > As cryptsetup can be used without initramfs (e.g. only home partition or > removable storage encrypted), the cryptsetup package doesn't depend on > "initramfs-tools, busybox" but merely recommends them.
If you want to cleanly support those two different use cases, it looks like the cleanest solution would be, to ship the initramfs integration in a separate binary package, say cryptsetup-initramfs-tools. This subpackage would have a strict dependency on initramfs-tools and busybox. The main cryptsetup package could have a recommends on that subpackage. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
