#2633 NORM Trial-3: TamTam needs R/W access to home directory, not included in Rainbow

Zarro Boogs per Child bugtracker at laptop.org
Thu Aug 2 01:40:51 EDT 2007


#2633: TamTam needs R/W access to home directory, not included in Rainbow
-----------------------+----------------------------------------------------
  Reporter:  mburns    |       Owner:  mburns   
      Type:  task      |      Status:  new      
  Priority:  normal    |   Milestone:  Trial-3  
 Component:  security  |     Version:  Build 239
Resolution:            |    Keywords:           
  Verified:  0         |  
-----------------------+----------------------------------------------------
Comment (by mburns):

 erp, thank you. I meant build 539.

 It will not be a problem but we will need to make a slight change.

 Here is our current thinking:
 $HOME must be mounted read-only. For persistant data, Rainbow will mount
 '/home/olpc/.sugar/default/X' (where X is your activity's unique service
 name) to /data in the container.

 In practice, that means we would like TamTam to change its base directory
 to /data and Rainbow (being outside any container) will ensure that it is
 properly mounted on activity load and saved to the home directory on exit
 appropriately. This bit is planned to be patched in the next day or so.

 For the time being (this week, essentially) it may be useful to have a
 check looking for the file '/etc/olpc-security' for testing. The presence
 of this file means that Rainbow is installed and presumably running and
 that you should set TAM_TAM_ROOT to '/data'). This looked like a pretty
 straightforward patch to your code, and I am working with it as a test
 activity for ensuring the above patches are working.

 We hope to flip the switch and have Rainbow installed and running by
 default with plenty of time for Trial 3 to work with you and other
 activity developers on a smooth transition.

 If this was unclear, please ask.

-- 
Ticket URL: <https://dev.laptop.org/ticket/2633#comment:3>
One Laptop Per Child <http://laptop.org/>



More information about the Bugs mailing list