On Sun, 2014-10-12 at 14:24 +0100, Ian Campbell wrote: > On Sat, 2014-10-11 at 21:58 +0100, Ben Hutchings wrote: > > On Sat, 2014-10-11 at 11:39 +0100, Ian Campbell wrote: > > > Source: initramfs-tools > > > Version: 0.116 > > > Severity: wishlist > > > > > > Dear Maintainer, > > > > > > Issues such as #762042 would be somewhat less critical for the affected > > > platforms if there was a mechnism for preseeding a list of additional modules > > > which should be included in the initrd, by adding them to > > > /etc/initramfs-tools/modules at install time. > > > > The installer already has a mechanism for adding modules to this list > > (register-module -i). > > So it does. Thanks for the pointer. But... > > > That doesn't allow arbitrary modules to be added by pre-seeding, and I'm > > not convinced that it should. That should only ever be a workaround, > > not something we expect to be widely used. You can accomplish such > > workarounds with late_command already. > > .. it doesn't seem to work for me from late_command. [...] > The modules are not present in /etc/initramfs-tools/modules either, so I > think late_command must be after whatever propagates the result of > register-module to the installed system too. [...] Indeed, that's what I would expect. What I meant was: 1. If you add code to e.g. hw-detect that determines that a module is needed in the initramfs, then register-module is the way to make this happen. 2. If the installer doesn't detect that a module is needed in the initramfs, and you as a user need a workaround, you can automate that by setting late_command (but not using register-module). Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa.
Attachment:
signature.asc
Description: This is a digitally signed message part