md5sum mismatch and new kernel installation

keeneadt · 03-01-2020, 03:32 AM

Hi everybody. Some questions about slackpkg and kernel upgrade.

1. Sometimes after upgrade i get warnings from slackpkg about md5sum of packages. As far as i understand it means that md5sum of original (remote) package differs from md5sum of downloaded (local) package. But if i check after upgrade version of such package i can see that regardless of md5sum mismatch i have new version of package installed. I don't think this is correct behavior. Shouldn't slackpkg stop upgrading or installing package if md5sum mismatch?

2. When it comes to kernel upgrade i use this instruction https://docs.slackware.com/howtos:sl...:systemupgrade . According to "System Upgrade using SlackPkg" section i should blacklist
kernel-generic
kernel-generic-smp
kernel-huge
kernel-huge-smp
kernel-modules
kernel-modules-smp
I wonder if kernel-firmware and kernel-headers should be in this list as well? Does firmware linked somehow to kernel version or not? If kernel-headers package is used for virtualbox or other stuff, should it be blacklisted as well?

Chuck56 · 03-01-2020, 06:55 AM

Quote:

Originally Posted by keeneadt

Hi everybody. Some questions about slackpkg and kernel upgrade.

1. Sometimes after upgrade i get warnings from slackpkg about md5sum of packages. As far as i understand it means that md5sum of original (remote) package differs from md5sum of downloaded (local) package. But if i check after upgrade version of such package i can see that regardless of md5sum mismatch i have new version of package installed. I don't think this is correct behavior. Shouldn't slackpkg stop upgrading or installing package if md5sum mismatch?

2. When it comes to kernel upgrade i use this instruction https://docs.slackware.com/howtos:sl...:systemupgrade . According to "System Upgrade using SlackPkg" section i should blacklist
kernel-generic
kernel-generic-smp
kernel-huge
kernel-huge-smp
kernel-modules
kernel-modules-smp
I wonder if kernel-firmware and kernel-headers should be in this list as well? Does firmware linked somehow to kernel version or not? If kernel-headers package is used for virtualbox or other stuff, should it be blacklisted as well?

1) regarding the occasional md5sum errors, are you running "slackpkg update" before install-new or upgrade-all?

2) new kernels should be downloaded then installed, not upgraded. If you plan to use a generic kernel then an initrd must be generated for the new kernel and in some cases an initrd is needed for the huge kernel. Your bootloader of choice should be updated to point at the new kernel. With a little planning the bootloader can offer a choice of either the working kernel or the new kernel at boot.

kernel-firmware can be upgraded and is usually kernel independent. kernel-headers can be upgraded and are used when a package is built/rebuilt.

Does that help?

keeneadt · 03-01-2020, 07:58 AM

Quote:

Originally Posted by Chuck56

1) regarding the occasional md5sum errors, are you running "slackpkg update" before install-new or upgrade-all?

2) new kernels should be downloaded then installed, not upgraded. If you plan to use a generic kernel then an initrd must be generated for the new kernel and in some cases an initrd is needed for the huge kernel. Your bootloader of choice should be updated to point at the new kernel. With a little planning the bootloader can offer a choice of either the working kernel or the new kernel at boot.

kernel-firmware can be upgraded and is usually kernel independent. kernel-headers can be upgraded and are used when a package is built/rebuilt.

Does that help?

1. My general upgrade scheme looks like

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade slackpkg
slackpkg upgrade-all

2. Thanks for clarifying. I'll remove firmware package from blacklist and i'll keep headers for virtualbox future compiling.