#9677 NORM Future : applying a kernel upgrade via rpm is risky

[Zarro Boogs per Child]

#9677: applying a kernel upgrade via rpm is risky
------------------------------+---------------------------------------------
           Reporter:  mikus   |       Owner:  dsd                               
               Type:  defect  |      Status:  closed                            
           Priority:  normal  |   Milestone:  Future Release                    
          Component:  kernel  |     Version:  Development source as of this date
         Resolution:  fixed   |    Keywords:                                    
        Next_action:  review  |    Verified:  0                                 
Deployment_affected:          |   Blockedby:                                    
           Blocking:          |  
------------------------------+---------------------------------------------
Changes (by mikus):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 A different build system is now being used than when this ticket was
 written.  I'll close #9677 [and open a new ticket if a problem shows up
 again.]

 Ticket #9677 was written against the XO-1.  More recently, I have several
 times applied (with 'yum') a new kernel to a then-current F11-on-XO1 build
 -- the newly applied kernel was used on subsequent boots.  So for F11-on-
 XO1 the specific #9677 problem seems to have been fixed.

 [[BR]][The XO-1.5 (at least on os108) still needs a manual copy operation
 following application of a new kernel with 'yum' -- that is because the
 install updates /boot, whereas OFW uses /bootpart.  But #9677 was *not*
 written against a system having a separate /bootpart partition.]

-- 
Ticket URL: <http://dev.laptop.org/ticket/9677#comment:3>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system