Re: [PATCH 1/1] support loading of custom initrd images

[Andrei Borzenkov]

05.02.2016 20:44, Christian Hesse пишет:
>>> +Give custom initrd images to be loaded in addition to the initrd image
>>> +found for the kernel. One use case is to load Intel ucode image.
>>> +  
>>
>> Is there any other use case? Both dracut and initramfs-tools already add
>> early cpio with microcode to generated initrd. This is bootloader
>> agnostic and better solution.
> 
> Running Arch Linux here, mkinitcpio does not do that.
> 
> The ucode has to be in uncompressed initramfs, so dracut and initramfs-tools
> use a concatenated image?

Yes.

> I think this was discussed for mkinitcpio, but denied for any reason. Would
> have to search for references...
> We have a downstream bug about dealing with Intel ucode in bug tracker. [0]
> 
> Nevertheless I have another use case:
> I do use Yubikeys in challenge/response mode to open my LUKS encrypted
> partition. [1] (This is not specific for mkinitcpio but works with dracut as
> well.) The challenges are stored in an extra initramfs. This is required if
> you want to update the challenge on every use - recompressing the initramfs
> on every boot is not a good option.
> 

Why your initrd cannot simply read this file from /boot itself?

signature.asc
Description: OpenPGP digital signature