On 02 Mar 2003 11:41:14 +0100 Bram Mertens <bram-mertens@linux.be> wrote:
Thx for the tip, I downloaded 3 files: k_deflt-2.4.20-18.i586.rpm kernel-source-2.4.20.SuSE-13.i586.rpm kernel-source-2.4.20.SuSE-13.src.rpm
According to the list of files of the k_deflt rpm contains a file named 'vmlinuz' that will be extracted to /boot/. This would overwrite my existing kernel, is there a way to prevent this?
I know I can rename the file /boot/vmlinuz to something like /boot/vmlinuz-2.4.19 and I know I would have to edit /etc/lilo.conf so the line 'image = /boot/vmlinuz' would become 'image = /boot/vmlinuz-2.4.19'.
But would I have to change/rename other files as well? My /etc/lilo.conf also contains a line for 'initrd' which appears to be in part the reason why I can't get my new kernel to boot.
Yes you can do this, but as you say, you must be careful to get the names matched up right when you edit lilo.conf. The other thing you need to watch out for: when you install the rpm it will probably want to delete the modules for the old kernel. So you have 2 choices: 1. Make a backup copy of the old modules directory, and after installing the new kernel, replace the old modules. 2. Just rip the rpm apart, extract the files, and manually install the new kernel and libraries. mc will do this, or if you need a script I have an rpm-ripper for you. -- use Perl; #powerful programmable prestidigitation