Please see: http://lists.laptop.org/pipermail/devel/2009-January/022334.html
I hope that is enough to get started. I don't know if the best place to continue discussion is in this thread or that. In any case I will be happy to help. The thread already has some good commentaries analyzing the results, so perhaps we should continue there. Best, Erik On Mon, Jan 12, 2009 at 4:48 PM, Ricardo Carrano <carr...@laptop.org> wrote: > Hi Paul, > >> > Just one XO froze (two times), but this unit seems problematic anyway. >> > I am attaching the stats for the other 28. >> > >> > There is a minor caveat (that is not actually related to the >> > nandblaster): Once you finish updating the XO that will be replicated >> > it woud be useful to put it in a state such that the XO-name and color >> > will be asked again after boot (otherwise you finsh with a lot of xos >> > with the same name and color). It is probably a matter of removing a >> > file. >> >> if you've booted the XO, there's more than that that's been >> cloned which might be a problem. (ssh host key, for example.) >> you should really nandblast images that haven't been booted. >> (erikg: did you finish your audit of what exactly gets changed?) >> > > True. I was so anxious to use the method that I didn't pay much > attention to that. > But If we don't boot the XO before the copying we'll lost the > opportunity to add some stuff. > If erikg has such a list, and we can revert some things, that would be > awesome! > > Cheers! > Ricardo > _______________________________________________ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel