Two questions about slackpkg
by hazel from LinuxQuestions.org on (#5MBPJ)
1) When I upgrade slackware-current, I always start by upgrading slackpkg itself. Then I update the gpg key. But then I have to run slackpkg update again, although all the downloaded lists should already be in the cache. Why is that?
2) What is the best way to deal with new kernels? Upgrading a kernel goes against my instincts; I'd much rather install the new kernel alongside the old one so that I have a fallback. So I blacklist the kernel and its modules to stop them being automatically upgraded. But then I can't install them either. I have to download them by hand and install them with installpkg. Is there a simpler way to do this?
2) What is the best way to deal with new kernels? Upgrading a kernel goes against my instincts; I'd much rather install the new kernel alongside the old one so that I have a fallback. So I blacklist the kernel and its modules to stop them being automatically upgraded. But then I can't install them either. I have to download them by hand and install them with installpkg. Is there a simpler way to do this?