On Fri, 09 Feb 2001 11:15:48 -0800, Curt Seeliger <[EMAIL PROTECTED]> wrote:
>
> '[EMAIL PROTECTED]' wrote:
>> ---------------------------------------------------------------------
>>                    Red Hat, Inc. Red Hat Security Advisory
>> 
>> Synopsis:          Three security holes fixed in new kernel
>> Advisory ID:       RHSA-2001:013-05
>> Issue date:        2001-02-08
>> Updated on:        2001-02-08
>> Product:           Red Hat Linux
>> Keywords:          sysctl ptrace mxcsr P4
>> Cross references:  
>> Obsoletes:         
>> ---------------------------------------------------------------------
>> 
>
> Folks,
>
> I've never updated a kernel, and since this is a work box I'm feeling
> unsettled about making such a fundamental change.  Is this like any
> other rpm update, or is there more to the procedure?   Does the
> procedure involve dead chickens perchance?

For detailed instructions, see:
http://www.redhat.com/support/docs/howto/kernel-upgrade/kernel-upgrade.html

Briefly:  
(1) You install the new kernel rpm rather than upgrading it (use "rpm -i kernel.rpm", 
not "rpm -U kernel.rpm").  This leaves the old kernel intact, so you can still run 
your system in case the new kernel doesn't work.
(2) Then you edit /etc/lilo.conf, adding a section for the new kernel (use the section 
for the old kernel as a template -- make the necessary modifications)
(3) Run lilo (/sbin/lilo).
(4) Reboot, select your new kernel according to the label you gave it in step (2).
(5) Dead chickens are optional.

If this is the first time you're doing this, read the detailed instructions before 
your start, but it is a safe procedure as long as you leave your old kernel on the 
system (install, don't upgrade).

If you haven't already done so, now is the time to make a boot disk (or two).  Test 
them before you try to install the new kernel.

__
Larry Grover, PhD
Assoc Prof of Physiology
Marshall Univ Sch of Med




_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to