[Trac #1155] let activities use compiled-in paths without conflict

[Zarro Boogs per Child]

#1155: let activities use compiled-in paths without conflict
---------------------------+------------------------------------------------
 Reporter:  AlbertCahalan  |        Owner:  krstic   
     Type:  defect         |       Status:  reopened 
 Priority:  normal         |    Milestone:  Untriaged
Component:  security       |   Resolution:           
 Keywords:                 |  
---------------------------+------------------------------------------------
Changes (by AlbertCahalan):

  * status:  closed => reopened
  * resolution:  invalid =>
  * summary:  use CLONE_NEWNS and bind mounts to give activities fixed-
              location bundle directories => let activities
              use compiled-in paths without conflict

Comment:

 This is to make porting trivial.

 Hardcoded paths like /bar would be kind of gross. (though why ban it?)

 Hardcoded paths like /usr/share/foo/bar and /etc/bar.conf are more
 realistic.

 Lots of existing apps have such paths. Usually they are determined at
 compile time. Often they can be changed via configure script or on the
 "make" command line.

 To reduce porting effort (and thus get more apps faster), compiled-in
 paths should be supported. It's best if such paths can be completely
 arbitrary.

 One might even use unionfs to safely allow writing to any file. All writes
 would of course be private to the app.

-- 
Ticket URL: <http://dev.laptop.org/ticket/1155#comment:6>
One Laptop Per Child <http://laptop.org/>