XO in-field upgrades

[C. Scott Ananian]

In the weekend I just read about Alex' plan for XO in-field upgrades.
The mailing list message is here:
   http://lists.laptop.org/pipermail/devel/2007-June/005381.html
I think the proposal deserves more discussion; in particular there are
some interactions with vserver and copy-on-write, as well as
networking (I really don't want the laptops broadcasting information
about what upgrade blobs they have on mDNS!  We should use a multicast
address at least...)  Also, I think we've discussed shipping binary
diffs rather than git's integral blobs, which may (or may not) be
incompatible with the proposal so far.  Fundamentally, I don't think
that re-using git's design philosophy wholesale is actually the Right
Thing for this application.

Has this already been discussed in more depth off-list?  I'd prefer to
get the relevant folks together for a quick f2f, since it seems like a
number of different groups are involved (networking, security, XO
build), but I can post a more detailed critique if we want to continue
the discussion on list instead.
 --scott
-- 
                         ( http://cscott.net/ )