#9677 NORM Future : applying a kernel upgrade via rpm is risky
Zarro Boogs per Child
bugtracker at laptop.org
Sun Nov 15 16:54:08 EST 2009
#9677: applying a kernel upgrade via rpm is risky
------------------------------+---------------------------------------------
Reporter: mikus | Owner: dsd
Type: defect | Status: new
Priority: normal | Milestone: Future Release
Component: kernel | Version: Development source as of this date
Resolution: | Keywords:
Next_action: review | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
------------------------------+---------------------------------------------
Changes (by Quozl):
* owner: => dsd
* next_action: never set => review
* component: not assigned => kernel
* version: Development build as of this date => Development source as of
this date
* milestone: Not Triaged => Future Release
Comment:
Fedora handles a kernel ''upgrade'' by removing the old kernel.
Fedora handles a kernel ''install'' by leaving the old kernel alone.
It is normal on Fedora and RHEL to direct people to use "rpm -i" instead
of "rpm -U", so that the old kernel can still be booted if required.
This ticket relates to #9648, for which the solution is that a manual step
must be done after a manual kernel upgrade and before reboot.
Your experience with XO-1.5 may have been using "rpm -i" instead of "rpm
-U". The former results in the old kernel being booted on reboot with all
modules present. The latter results in the old kernel being booted on
reboot with no modules present ... because:
* the new kernel was placed in a directory by RPM that was not used by
the boot,
* the old kernel was not in that directory that RPM wanted to remove it
from,
* the old kernel modules were present and removed by RPM.
Assigning to dsd since it is his XO-1 kernels being referred to.
--
Ticket URL: <http://dev.laptop.org/ticket/9677#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list