XO in-field upgrades

[C. Scott Ananian]

On 6/25/07, Noah Kantrowitz <kantrn at rpi.edu> wrote:
> It is worth noting we are not using vhashify or any of the other util
> scripts. The rainbow daemon sets up the chroot for each activity itself.
> We are a bit non-standard in that we are doing process-level
> containerization, instead of a more guest-OS system like many vserver
> users (most?).

So we're manually copying (or hard linking?) files into the chroot on
every process activation?  Won't this wear down our flash?  (Or are
all our chroots in RAM?)  How do/can we update the libraries/etc used
by the process in the container?  Are services (like the proposed
upgrade daemon) chrooted as well?  If so, how do upgraded files get
out of the chroot?

Could you give me a pointer to the design docs on rainbow/etc?
  --scott
-- 
                         ( http://cscott.net/ )