On 2/3/19 3:11 PM, Ben Koenig wrote:
Yes that is correct, however it is recommended to blacklist the kernel for
slackpkg upgrades.
Generally speaking (and there are exceptions) you should avoid updating the
kernel unless you have a specific reason to do so.
Nobody running a mission-critical system updates anything without first
looking at the changes. The reason is what you just found out, stuff breaks.
if this is a home system, then blacklisting kernel updates from the normal
slackpkg system is reasonable. You can always specify kernel updates if and
when you need to.
Take a look at the files in /etc/slackpkg/. These are the configuration
files for slackpkg, you can modify the behavior of the upgrade-all command
by blacklisting stuff. It even has an example of how you would blacklist
the kernel packages, since it is common practice.
Remember that this isn't blacklisting all kernel updates, you can always
upgrade when you feel the need and have time to do so.
I don't have it blacklisted. I just have a mental todo list when I do
updates. if the kernel was updated .. I copy the new one to my EFI
partition and re-run the nvidia install script (I don't actually use the
slackbuild).
Thanks. Still much to learn.
--
Regards,
Dick Steffens
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
