[rhn-users] Interrupted up2date when updating kernel

[Alfred Hovdestad]

I'm not sure about the System.map.  It might be required before you 
boot.   You can find out what gets done in the kernel install package 
with the rpm -q --scripts command (I'm running 2.4.21-32.0.1.EL):

$ rpm -q --scripts kernel-2.4.21-32.0.1.EL
preinstall scriptlet (using /bin/sh):
/sbin/modprobe loop 2> /dev/null > /dev/null  || :
postinstall scriptlet (using /bin/sh):
cd /boot
[ -x /usr/sbin/module_upgrade ] && /usr/sbin/module_upgrade
[ -x /sbin/mkkerneldoth ] && /sbin/mkkerneldoth
[ -x /sbin/new-kernel-pkg ] && /sbin/new-kernel-pkg --mkinitrd --depmod 
--install 2.4.21-32.0.1.EL
exit 0
preuninstall scriptlet (using /bin/sh):
/sbin/modprobe loop 2> /dev/null > /dev/null  || :
[ -x /sbin/new-kernel-pkg ] && /sbin/new-kernel-pkg --rminitrd 
--rmmoddep --remove 2.4.21-32.0.1.EL
exit 0


If the new kernel doesn't boot, you can either boot up the old kernel, 
remove the new kernel, and re-isntall it or you can try running the 
postinstall script by hand.  If it were me, I would try to uninstall the 
new kernel and re-install it (but maybe I am just paranoid).

    Alfred



Barry Byrne wrote:
> That's what I was thinking. I will try this tomorrow.
> 
> One other question, I notice a System.map file which is a symbolic link to
> another file System.map-2.4.21-27.0.2.Elsmp . There is a corresponding
> System.map-2.4.21-32.0.1.Elsmp - I presume I should change this symbolic
> link to point to the relevant file? If so, is it OK to leave this until
> after I verify the new kernel will boot (selecting from boot menu)?
> 
> Once again, thanks for the help.
> 
> Cheers,
> 
> Barry
> 
> 
>>-----Original Message-----
>>From: rhn-users-bounces at redhat.com 
>>[mailto:rhn-users-bounces at redhat.com] On Behalf Of Alfred Hovdestad
>>Sent: 06 September 2005 16:37
>>To: Red Hat Network Users List
>>Subject: Re: [rhn-users] Interrupted up2date when updating kernel
>>
>>Hi Barry:
>>
>>If the entry for the new kernel has been added to 
>>/boot/grub/grub.conf 
>>then you should be able to select it on boot.  I assume that you are 
>>running the smp kernel (else why would you have it installed?).  You 
>>should then be able to change the default entry in grub.conf 
>>to point to 
>>the new kernel.
>>
>>    Alfred
>>
>>
>>
>>Barry Byrne wrote:
>>
>>>Alfred:
>>>
>>>Thanks for the input. However, this fails with the message:
>>>
>>>	Testing package set / solving RPM inter-dependencies...
>>>	########################################
>>>	RPM package conflict error.  The message was:
>>>	Test install failed because of package conflicts:
>>>	package kernel-utils-2.4-8.37.12 is already installed 
>>>
>>>It would appear that the packages are installed. I will try a reboot
>>>tomorrow morning when the machine is less busy and see if I 
>>
>>can bring up the
>>
>>>newer kernel. The entries seem to have been added to 
>>
>>/boot/grub/grub.conf
>>
>>>for the new kernel, but the default parameter still points 
>>
>>to the older
>>
>>>kernel, I presume if I just change this it should use the new one.
>>>
>>>Thanks again,
>>>
>>>Barry
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: rhn-users-bounces at redhat.com 
>>>>[mailto:rhn-users-bounces at redhat.com] On Behalf Of Alfred Hovdestad
>>>>Sent: 06 September 2005 16:02
>>>>To: Red Hat Network Users List
>>>>Subject: Re: [rhn-users] Interrupted up2date when updating kernel
>>>>
>>>>You should be able to "force" the update.
>>>>
>>>>up2date -f kernel
>>>>up2date -f kernel-smp
>>>>up2date -f kernel-source
>>>>
>>>>  Alfred Hovdestad
>>>>  University of Saskatchewan
>>
>>_______________________________________________
>>rhn-users mailing list
>>rhn-users at redhat.com
>>https://www.redhat.com/mailman/listinfo/rhn-users
> 
> 
> _______________________________________________
> rhn-users mailing list
> rhn-users at redhat.com
> https://www.redhat.com/mailman/listinfo/rhn-users