[FLSA-2004:1284] Updated kernel resolves security vulnerabilities

ral77 ral77 at bellsouth.net
Fri Mar 5 04:38:15 UTC 2004


Troels Arvin wrote:

>On Wed, 03 Mar 2004 02:05:42 -0500, SC Web Services wrote:
>
>  
>
>>So I did a reboot, but for some reason, it continues to boot the second
>>entry, image=/boot/vmlinuz-2.4.20-28.7. Can this have something to do with
>>the name too long issue?
>>    
>>
>
>Yes. Remove all occurrences of ".legary" from lilo.conf and re-run "lilo".
>
>  
>
Will this apply to /boot/grub.conf as well after the updated kernel is 
installed (remove .legacy from kernel entry) ?
I have both rh72 with lilo and a rh8 server using the grub bootloader.
In the past when I  downloaded and updated a kernel manually it was rpm 
-ivh kernel-2.4.20-*. This way the previous kernel is still available as 
backup , would a rpm -Fvh overwrite the kernel-2.4.20-28.7.
thx's
Robert 

<snip>







More information about the fedora-legacy-list mailing list