On 03/02/2003 06:41 PM, Bram Mertens 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?
Not installing ;-) . It is not a bad thing. You will also be replacing the modules that would be needed by that kernel image, so renaming just the vmlinuz file wouldn't accomplish much. Since it is an rpm, you could always re-install your presently used kernel if things go bad (but I doubt it as I am using that one now and really like it so far).
But would I have to change/rename other files as well?
You would need to use a 'optioned' mkinitrd, as well as keep the 2.4.19 module tree, but this will be uninstalled by installing the newer kernel. They would conflict otherwise.
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.
Was this a self compiled model?
What is the difference between the 2 kernel-source-rpms? If I would like to compile the kernel myself, which one would I have to install?
kernel-source-2.4.20.SuSE-13.i586.rpm -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.