Customization stick
| Please copy/paste "{{Translationlist | xx | origlang=en | translated={{{translated}}}}}" (where xx is ISO 639 language code for your translation) to Customization stick/translations | HowTo [ID# 116527] +/- |
The customization key allows you to install your own set of activities and library content on top of a signed OLPC build.
Preparing the key:
- Unpack customization-1.zip into the root directory of a USB key.
- This will create an empty subdirectory 'bundles' and a subdirectory 'boot' containing two files 'runos.zip' and 'actos.zip'.
- Add 'fs.zip' and 'osXYZ.img' from the base build you want to install.
- This is optional. If no signed base build is present, the activities will still be installed.
- For example, the files for build 656 are at http://download.laptop.org/xo-1/os/official/656/jffs2/
- Only official releases are signed, and have an associated 'fs.zip' file.
- Drag the .xo files (activity bundles) and .xol files (library bundles) you want to install into the 'bundles' directory.
- If you create a zip file containing 'frame00.565' through 'frame26.565' and place it in 'bundles' with a name ending in '.pb', you can customize the boot sequence. You might also replace the shutdown graphic.
Using the key:
Once you've created your usb stick(s) in this way:
- Insert the stick into a powered-off XO
- Turn the machine on while holding down all four game pad keys to update to newer build and customize.
The machine will erase all contents of the flash including any existing activation lease or developer key on the XO, install the base build, and then install your custom activity and content set. It will then power-off, and you can remove the stick and move on to the next XO.
- Or, turn the machine on without holding the four game pad keys to customize only.
- Or, for developer machines only you can customize by holding the x game key to simulate security.
NOTE: If your machine is unactivated, this key does not perform the activation step for you. You will need to Activate your XO in order to get the machine to boot after this process. Note that you can not put your activation lease on the customization key and expect it to work; it will boot the customization routine instead of booting into the activation routine. Your activation lease file (lease.sig) must be on a different key (or else you must temporarily rename the 'boot' directory on the customization key).