Peabody Setup: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
{{delete}}
[[Category:Testing]]
===Preparing the XOs===
===Preparing the XOs===



Revision as of 04:59, 4 August 2008

  Trashcan.png A request has been made for this page to be deleted.
If you disagree with its deletion, please explain why on its talk page.
Before deleting verify that no links will break.

Preparing the XOs

Preparing an out of the box XO requires:

  • Labeling. There are tags labeled X01-X100
  • Activation
  • Upgrade
  • Customization

For each of these steps we have a special bootable USB stick, which performs the corresponding task automatically.

We have the following bootable keys:

  • Collector key
  • Developer key
  • Upgrade key
  • Customization key
  • Action key

A stick cannot be a combination of the above.

The process of using the key involves simply

  1. Plugging the stick while the XO is turned off.
  2. Turning it on, and in most cases everything is done automatically.


Multi key

These keys have different contents. To convert from one key to the other you would have to erase the original content, and replace with the new content.

In the warehouse we will have several USB sticks which will include the contents of all 5 keys in a folder called keys. To convert the stick to a special bootable key you simply need to copy the contents of the corresponding folder in the root directory of the USB key. For example

  • if you wanna create a collector key, you must copy the boot directory located in /key/1.collector key to the root dirrectory
  • if later you wanna create a different key, you must first delete the boot directory


The Keys

You should use each key in the following order

Collector key

This gets the serial number in order to create an activation code/developer key.

  1. Plug the stick in a turned off XO, and turned it on. The data will be stored and the XO will be automatically rebooted.
  2. You can move on the next XO using the same stick, until you are done.
  3. It is advisable if you keep track of the order of the XOs at which you put the key. Every time you apply the collector key you should stick a name tag on the XO, and keep the order. In the end we can pair serial numbers with names.
  4. In the end we can use the LAPTOPS.DAT file created in the usb to create a developer key.

Developer key

For every LAPTOPS.DAT file we will create a develop.sig file.

  1. Paste this file in the security directory in the developer key
  2. You can apply the same key in all XOs from which you created the LAPTOPS.DAT file.
  3. Plug the stick when the XO is turned off, and turn it on.
  4. While it says "Type the ESC key to interrup" press the ESC key.
  5. Type disable-security and enter. The XO will reboot automatically.
  6. Again, while it says "Type the ESC key.." press the ESC key.
  7. Type for a second time disable-security and enter. The XO will reboot automatically
  8. Do not let it boot. Turn it off again by holding the Power button.

Upgrade key

All XOs will be upgraded to the latest Update.1 build 700.

  1. Plug the key while the XO is off, and turn it on
  2. After several minutes the XO will upgrade and turn off automatically.

Customization key

After the upgrade the XOs have no activities. You will have to install them separately using this key.

  1. Plug the key while the XO is off, and turn it on
  2. It will install the activities and turn off automatically
  3. You can now finally turn the XO on!!

Action key

Sometimes it is useful to add certain scripts or set some flags/configurations at boot. This can be automated with the action key. The

  1. Plug the stick in a turned off XO and turn it on.
  2. The key will execute the action script located in the root directory. You can edit it accordingly.
  3. The rc.local file includes code to be executed at boot.
  4. The current action key will copy in the XO several scripts that can be useful in testing, but you can edit at will.