A lot of work going on behind the scenes on an upcoming maintenance release of slackpkg-2.84 by rworkman and the downstream impacts to slackpkg+-1.7.0 by zerouno:
slackpkg 2.84.0_beta1 - Testing Wanted -
https://www.linuxquestions.org/quest...ed-4175643527/
Looks like the team is up to beta6 on slackpkg and is proposing some changes to blacklist functionality. I'm not using the beta but I have spent some time cleaning up my blacklists recently. My most unusual blacklist is for an old Acer Aspire One netbook that is running 32 bit, 14.2-smp. I cut out the comment lines for brevity.
Code:
kernel-firmware-20160628git
kernel-generic-[0-9]+
kernel-generic-smp-4.4.14_smp
kernel-headers-[0-9]+
kernel-headers-4.4.14_smp
kernel-huge-[0-9]+
kernel-huge-smp-4.4.14_smp
kernel-module-ecryptfs
kernel-modules-[0-9]+
kernel-modules-smp-4.4.14_smp
kernel-source-4.4.14
kernel-source-4.4.14_smp
[0-9]+_SBo
[0-9]+_1alien
kde-l10n
calligra
sbopkg
Usually "slackpkg update, install-new upgrade-all & clean-system" does the trick on 14.2 unless a kernel upgrade is thrown in the mix.
For the kernel upgrades I usually "slackpkg download kernel" then select generic, huge, modules & source. I use installpkg for the downloaded files and "mkinitrd -F x.x.x" for the new kernel. LILO is updated with the old and new kernel just in case I need to fallback after reboot. I picked up this habit from all the smart folks here at LQ that shared their kernel administration process over the years.
My blacklist prevents all the original 32 bit, 14.2 kernel files and the more recent non-smp kernels from showing up in the slackpkg download list. So what does your blacklist look like & why?