#6470 NORM Never A: olpc-update doesn't let users manage their software builds

[Zarro Boogs per Child]

#6470: olpc-update doesn't let users manage their software builds
------------------------------+---------------------------------------------
  Reporter:  gnu              |       Owner:  cscott                           
      Type:  defect           |      Status:  new                              
  Priority:  normal           |   Milestone:  Never Assigned                   
 Component:  upgrade utility  |     Version:  Development build as of this date
Resolution:                   |    Keywords:                                   
  Verified:  0                |    Blocking:                                   
 Blockedby:                   |  
------------------------------+---------------------------------------------

Comment(by mikus):

 Replying to [comment:5 cscott]:
 > The "cross-build" stuff is because your editor doesn't do the "write to
 a temp file and move" mechanism of editing files; it is editing them in
 place instead.  The hardlinked cow system can't protect you from that; you
 need to be careful instead.

 Did not understand your intent here.

 The editor I use is 'vi'.  I believe it is quite careful about protecting
 an edit session from a different session simultaneously changing that same
 file.  I did not get any such warnings.

 --------

 My "empirical" understanding (from ls -la /versions) is that there are at
 least TWO directory trees (characterized by differing 32-byte
 identifiers).  I replaced __both__ (via 'olpc-update').  Yet (unless I
 misremember), after booting Joyride and editing its "in-core"
 /etc/profile, when I booted Update.1 I think I saw my changes already in
 its "in-core" /etc/profile.  I had assumed that when booting a build with
 a different 32-byte identifer, that all "in-core" modules would be loaded
 anew.
 .

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