Nand blaster with 30 XOs

Ricardo Carrano carrano at
Mon Jan 12 16:48:10 EST 2009

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!


More information about the Devel mailing list