View source for Imaging/Side effects

'''Imaging laptops is not supported by OLPCA's deployment support team.  However, it sometimes works in limited testing.'''

== Introduction ==
We haven't worked on figuring out what pieces of the system are touched, so copying the machines can have unintended side effects.  It seems that nearly everyone who tries to distribute images by cloning runs into some oddities.

There are a number of changes made to system files during the first boot of the machine which you might not want to copy between machines. SSH keys, for instance, are generated once at first boot on every XO.  Also, hardware-dependent information from the firmware is cached on the laptop after first boot.

That said, it also seems that this method of customization is the most appealing and straightforward, and matches some of the existing desktop deployment practices for ICT in education.

== Procedure ==


To correct for the side-effects you may either prepare the source system before it is cloned, or fix each target system after it is cloned.  If you are cloning to more than one target, then it is more efficient to modify the source system, so that the modifications are cloned.  The same actions can be used in both cases:

{{Template:Software_Side_Effects_Fixes}}

To fix loss of collaboration and first boot name prompt on an already cloned target system, start Terminal, enter the command:

 rm -rf .sugar .gconf/desktop/sugar

and then shutdown using a double power button press.

== See Also ==

* http://lists.laptop.org/pipermail/devel/2008-March/012200.html (Michael Stone, survey of unintended boot state changes)
* http://lists.laptop.org/pipermail/devel/2008-April/012957.html (Bryan W. Berry, regarding /security)
* http://lists.laptop.org/pipermail/devel/2009-January/022334.html (A comparison of changes caused by first boot)
* [[/13.2.1|analysis of filesystem changes in 13.2.1 first boot]