[Slackbuilds-users] Edit suggested of intel-microcode.SlackBuild

Andrzej Telszewski andrzej at telszewski.com
Wed Sep 6 13:13:51 UTC 2023

On 06/09/2023 14:29, fourtysixandtwo wrote:
> I second Didier's suggestion.
> Here's  a snippet from the grub docs, the default images it looks for 
> are at the bottom:
>      List of space-separated early initrd images to be loaded from
>      '/boot'.  This is for loading things like CPU microcode, firmware,
>      ACPI tables, crypto keys, and so on.  These early images will be
>      loaded in the order declared, and all will be loaded before the
>      actual functional initrd image.
>      'GRUB_EARLY_INITRD_LINUX_STOCK' is for your distribution to declare
>      images that are provided by the distribution.  It should not be
>      modified without understanding the consequences.  They will be
>      loaded first.
>      'GRUB_EARLY_INITRD_LINUX_CUSTOM' is for your custom created images.
>      The default stock images are as follows, though they may be
>      overridden by your distribution:
>           intel-uc.img intel-ucode.img amd-uc.img amd-ucode.img 
> early_ucode.cpio microcode.cpio
> Cheers

Still, I'm not that fast about changing the name.
This name is _kinda_ standard in Slackware for quite some time
and is used by default in _/etc/mkinitrd.conf_

Any suggestions?
Maybe a copy or configurable name of the output file in the SlackBuild?

Symlinking is out of scope, since the boot partition will often be 
FAT32, that does not support symlinks.

More information about the SlackBuilds-users mailing list