[SOLVED] Keep kernel-* packages for 3.2.29 and 3.2.45 side by side?
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Keep kernel-* packages for 3.2.29 and 3.2.45 side by side?
I'm normally using slackpkg to keep my machines upgraded (on Slackware stable). Now recently there have been two consecutive kernel upgrades, with all the kernel-* 3.2.29 packages replaced by kernel-* 3.2.45 packages.
On a "normal" machine I don't care if the old kernel-* packages are replaced by the updates. But I'm running a few virtual machines as "build boxes", and I'd like to keep the old and the new kernel installed, to be able to boot on both, in order to build kernel modules for machines still running the 3.2.29 kernel.
In other words, is there a way to make Slackware behave like a RHEL/CentOS machine, where 'yum upgrade' updates all packages except the kernel packages, where new packages are merely installed alongside older versions?
Distribution: Slint64-14.2beta2 on Lenovo Thinkpad W520
I'd try to blacklist kernels in /etc/slackpkg/blacklist but when an upgrade shows, install it (kernel+ modules) with installpkg or slackpkg install (neither upgradepkg nor slackpkg upgrade, of course). In addition you will just have to change the stanza in /etc/lilo.conf to give the full path of the old kernel instead of /boot/vmlinuz before running lilo manually. Then I think that you would just have to set the kernel against which you build the new modules as a build option.
OT: I need a proofreader for French translation of Slackware scripts' messages in slint. And I know that you would catch any typo, mistranslation or clumsiness
Last edited by Didier Spaier; 06-19-2013 at 09:51 AM.
One trick I use in order to help in not having any upgradepkg accidents with my home-grown kernel packages is to slightly modify the package name so that the version number is included in the package name field and not the version field, i.e.
Doing it this way means I can use "upgradepkg --install-new *" without fear of a new kernel clobbering the old one.
Always use installpkg for kernel and kernel-modules. Blacklist them in /etc/slackpkg.conf .
Thanks, Eric. According to the documentation, I've been living dangerously until now. I've been using slackpkg upgrade-all to upgrade even the kernel, then hardcoded the kernel version in mkinitrd.conf and rebuilt the initrd before the first reboot.
I have my kernel packages blacklisted in /etc/slackpkg/blacklist to keep them from being overwritten but there are two instances where I do allow slackpkg to upgrade them for me. Firstly if I have just performed a clean install the first thing I do is update the system anyway and since I haven't yet even switched to the generic kernel I go ahead and let slackpkg upgrade my kernel. It just makes for a more clean and tidy install for me. Secondly, if the upgrade is to the same kernel version like recently... 3.2.45(1) to 3.2.45(2) to 3.2.45(3) I will go ahead and allow slackpkg to upgrade it.
Now this is strange. On a machine running the stock 3.2.29 kernel from the installation disc, I downloaded the updated kernel sources from patches/linux3.2.45 and tried to install them manually using installpkg.
Here's what I get:
[root@virtualbox:packages] # ls
[root@virtualbox:packages] # installpkg kernel-source-3.2.45_smp-noarch-3.txz
Verifying package kernel-source-3.2.45_smp-noarch-3.txz.
xz: (stdin): File format not recognized
Installing package kernel-source-3.2.45_smp-noarch-3.txz:
WARNING: Package has not been created with 'makepkg'
Package kernel-source-3.2.45_smp-noarch-3.txz installed.