Originally Posted by stormtracknole
Pardon my lack of knowledge on this, blame it on depending on yum for kernel updates in Fedora.
Anyway, can someone provide a little more in dept step by step on how to apply this patch? I read the README.TXT and am I just a tad confuse. Do I have to move the .config file to all of the kernel-* directories? Is it easier to upgrade kernel from the current tree? I'm running a Slackware server and I don't want to fork it by not doing the update correctly. Thanks in advance!
The way to update this depends on your setup.
If you have made a custom kernel image based off of the default slackware kernel sources, then you should use the patch as described in the README to patch your sources in order to rebuild your custom kernels.
If you are using a custom kernel that is a different version then you should patch or upgrade up to the version that is needed. The articles that Lenard linked to should lead you where to find what you need. If you are in this boat you could just build from the newest stable kernel from kernel.org.
However, I'm assuming you are using the stock slackware kernel images. In that case, you can simply download and install the newest package that you need
(looks like mRgOBLIN left directions for installing). Look in the security advisory for information on where to download it.
To see what a slackware package looks like on the inside you can you explodepkg
or just use tar
. explodepkg basically just untars the package and tells you that it isn't running the install script.
For instance, if I don't feel like unpacking a package to see a list of its contents I can just use tar
tar zvtf kernel-generic-smp-184.108.40.206_smp-i686-2_slack12.0.tgz
drwxr-xr-x root/root 0 2008-02-11 17:16 ./
drwxr-xr-x root/root 0 2008-02-11 17:16 boot/
-rw-r--r-- root/root 2088024 2008-02-11 17:16 boot/vmlinuz-generic-smp-220.127.116.11-smp
-rw-r--r-- root/root 813610 2008-02-11 17:16 boot/System.map-generic-smp-18.104.22.168-smp
-rw-r--r-- root/root 72764 2008-02-11 17:16 boot/config-generic-smp-22.214.171.124-smp
drwxr-xr-x root/root 0 2008-02-11 17:16 install/
-rw-r--r-- root/root 1143 2008-02-11 17:16 install/slack-desc
-rw-r--r-- root/root 279 2008-02-11 17:16 install/doinst.sh
the install directory is a special directory where the package description (slack-desc) and the install script (doinst.sh) are located. The rest of the files/directories represent where stuff would be installed. So, as you can see you will have three entries installed to /boot.
Now if you want to see what the doinst.sh script does, you can use tar to extract that file to stdout with the -0
tar -zOx install/doinst.sh -f kernel-generic-smp-126.96.36.199_smp-i686-2_slack12.0.tgz
( cd boot ; rm -rf vmlinuz )
( cd boot ; ln -sf vmlinuz-generic-smp-188.8.131.52-smp vmlinuz )
( cd boot ; rm -rf System.map )
( cd boot ; ln -sf System.map-generic-smp-184.108.40.206-smp System.map )
( cd boot ; rm -rf config )
( cd boot ; ln -sf config-generic-smp-220.127.116.11-smp config )
Notice that it only extracted the install/doinst.sh file because it was specified (otherwise all of the files would have been extracted to stdout).
As you can see the doinst.sh simply links vmlinuz, System.map, and config to this kernels files under /boot. So, this supports my statement of why you can just install this package (or one similar) if you are using the stock slackware kernels.