On Thu, Sep 24, 2009 at 12:39 PM, Jonas Meurer <jo...@freesources.org> wrote: > thanks for your bugreport. Thank you for volunteering your time to provide this package to all of us :)
> i consider to change the default way to include crypto modules into the > initramfs though: in future simply all available crypto modules will be > added into the initramfs. that slightly increases size of the initramfs, > [...] > available as a configurable alternative, for minimal systems where > initramfs size matters. great! > unfortunately your suggestion is not an > option. in order to support system which do have some/all crypto support > compiled into the kernel adding modules to the initramfs will remain > quiet. uhm .. right, and I guess there is no way to check /boot/config* or the system map to verify if the needed code is in the kernel? Why not add a configuration parameter for all those who are using stock kernels and don't have crypto modules compiled in? Eg, the choice seems to be between (1) 'we remain silent, the output looks cool, but we might make the system unusable without warning the user' or (2) 'we sometimes output warnings that we shouldn't output'. If it was me, I'd pick 2, rather than 1 :-), maybe adding a text like 'watch out, if you have modules compiled it, you can probably ignore this warning', or better an option somewhere that defaults to 'yes, spit warnings for missing modules'. Anyway, Thanks! Carlo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
