Kernel Patching

[John Seth]

Slackware doesn't use Grub, only LILO ;)

I would suggest subscribing to Slackware's security email list, here's the
excerpt from installing the updated package:

--- [slackware-security]  Kernel security update  (SSA:2003-336-01) ---

Use upgradepkg to install the new kernel, kernel-modules, and alsa
packages. After installing the kernel-ide package you will need to run
lilo ('lilo' at a command prompt) or create a new system boot disk
('makebootdisk'), and reboot.

If desired, a kernel from the kernels/ directory may be used instead.  For
example, to use the kernel in kernels/scsi.s/, you would copy it to the
boot directory like this:

cd kernels/scsi.s
cp bzImage /boot/vmlinuz-scsi.s-2.4.23

Create a symbolic link:
ln -sf /boot/vmlinuz-scsi.s-2.4.23 /boot/vmlinuz

Then, run 'lilo' or create a new system boot disk and reboot.

-------- END COPY --------

Basically, use upgradepkg, then rerun 'lilo' from the command prompt, and
reboot.  Try 'uname -a' then and see what you get.


--
<? print(pack("c*", 74,117,115,116,32,/* Tony Evans                  */
 65,110,111,116,104,101,114,32,80,72, /* Linux/Web Implementation    */
 80,32,72,97,99,107,101,114,46,10));  /* http://www.phoenixwing.com/ */ ?>





On Sun, 7 Dec 2003, Kevin E. Glosser wrote:

> On Sun, 2003-12-07 at 12:40, Frank Kumro wrote:
> > I just patched my kernel to version 2.4.23 from the default version in
> > slackware 9.1 of 2.4.22 - Correct me if im wrong but shouldnt uname -r
> > return 2.4.23 not 2.4.22?
>
> Yes, assuming you rebooted, assuming GRUB or LILO was updated to point
> to the NEW kernel.
>
> I'm not familiar with Slackware, but sounds like you used an automated
> update utility? Those, well at least Redhat/Fedora's, also fix GRUB and
> LILO after updating the kernel.
>
> I would check to see which kernel GRUB or LILO is using.
>
> GRUB: /boot/grub/grub.conf
>
> LILO: (think config file is in /etc , been a while since I used it)
>
> Also have to issue the command "lilo" after you make changes to lilo
> configuration file to make them active. Not so with grub.
>
> KEG
>
>