I read in the changelog
Wed Sep 21 15:54:06 UTC 2016
a/mkinitrd-1.4.8-x86_64-9.txz: Rebuilt.
When generating the initrd, include dmsetup whenever LUKS is requested.
Thanks to TracyTiger for the bug report and Eric Hameleers for the patch.

Does this mean that anyone with LUKS/LVM should re-run mkinitrd immediately after installing the update? I ask because that is my setup and I haven't really had any issues with booting.

As a second question, my 100M /boot partition is starting to be full, due to three kernels/modules/headers/source. I build special named initrd's for each kernel. I'm comfortable with only the running generic (4.4.20) and the past (4.4.19) and deleting all older kernels/header/modules/firmware and even the huge kernel. I also suspect that because of running -current I may need to have many kernels before the next stable release.

Advice and insight are always appreciated.

I don't think you need to update your initrd just because you updated your mkinitrd. If your initrd is working don't touch it.

1 members found this post helpful.

bamunds,
I agree with BlackRider. Don't worry about it! It's an arguably minor bugfix to mkinitrd, and in no way affects the reliability of your current initrd. When you next build an initrd for your next kernel, you most likely won't even notice the difference.
Interestingly, you can read about the genesis of this latest fix to mkinitrd in a recent thread here:
https://www.linuxquestions.org/quest...on-4175589693/
Regarding your /boot, I too, run -current :-) My advice is don't delete anything from /boot!
Use pkgtool to select the kernels and etc, you wish to un-install (pardon if that's what you actually meant..)
Viva Slackware!

@STDOUBT I didn't realize that kernels/modules/headers/firmware were available for removal with pkgtools, neat.
I'll assume this also means correcting my lilo.conf?
I am interested if I should specifically remove "huge" or if there are benefits to leaving it in place as a fallback, or should one always leave their original "generic" kernel?
Oh-- am I correct that the firmware for 4.4.19 and 4.4.20 is the same?
Thanks.

I've read the original thread, thanks for the reference. Interesting. I didn't have the same results as that thread's OP when using the generator. The generator did output the -L option to be included. I wonder if AlienBob's liveslak PLASMA5 iso mkinitrd is already patched, so the upgrade won't make a difference? Either way, I'm not planning to re-run mkinitrd since my boot is working without trouble. Then only thing I do notice is my system doesn't actually stop console message when the LUKS passphrase is requested, but I've lived with that for two years on my machines I simply wait until the phrase rolls by and then start typing and the console always pickup my keystrokes and proceeds. I guess someday I should figure out how to use a boot usb key for LUKS, and save the typing. LOL.

If you are using LVM, you won't see the issue.

Everything on a stock Slackware install is removable using a package

Personally, I would leave huge in place as a fallback; just as I would leave the original stock kernel packages available as fall backs if you start using custom versions. Removing the huge kernel package will only save you around 10MB, and leaving it in place won't affect anything (but removing it won't really either).

The firmware is done independent of the kernel. It's updated whenever Pat decides to pull newer firmware from kernel.org (assuming they have updates there). If the dates are the same, there's no need to "upgrade" it as it is the same package.

Thanks bassmadrigal. I plan my pkgtool delete appropriately to leave base system in place, but eliminate upgrades except current kernel. That was the advice I was hoping to receive. Cheers