Peabody Setup: Difference between revisions
(New page: 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. #Plug the stick in a turned off XO, an...) |
No edit summary |
||
(5 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
[[Category:Testing]] |
|||
This documents the steps taken to prepare laptops for the [[Collaboration Network Testbed]] in Jan. 2008. |
|||
===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 |
|||
#Plugging the stick while the XO is turned off. |
|||
#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 <code>keys</code>. 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 <code>boot</code> directory located in <code>/key/1.collector key</code> 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 |
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. |
This gets the serial number in order to create an activation code/developer key. |
||
Line 9: | Line 47: | ||
#In the end we can use the LAPTOPS.DAT file created in the usb to create a developer key. |
#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. |
For every LAPTOPS.DAT file we will create a develop.sig file. |
||
Line 21: | Line 59: | ||
#Do not let it boot. Turn it off again by holding the Power button. |
#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. |
All XOs will be upgraded to the latest Update.1 build 700. |
||
#Plug the key while the XO is off, and turn it on |
#Plug the key while the XO is off, and turn it on |
||
#After several minutes the XO will |
#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. |
|||
#Plug the key while the XO is off, and turn it on |
|||
#It will install the activities and turn off automatically |
|||
#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 |
|||
#Plug the stick in a turned off XO and turn it on. |
|||
#The key will execute the <code>action</code> script located in the root directory. You can edit it accordingly. |
|||
#The <code>rc.local</code> file includes code to be executed at boot. |
|||
#The current action key will copy in the XO several scripts that can be useful in testing, but you can edit at will. |
Latest revision as of 21:15, 29 January 2009
This documents the steps taken to prepare laptops for the Collaboration Network Testbed in Jan. 2008.
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
- Plugging the stick while the XO is turned off.
- 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.
- Plug the stick in a turned off XO, and turned it on. The data will be stored and the XO will be automatically rebooted.
- You can move on the next XO using the same stick, until you are done.
- 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.
- 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.
- Paste this file in the security directory in the developer key
- You can apply the same key in all XOs from which you created the LAPTOPS.DAT file.
- Plug the stick when the XO is turned off, and turn it on.
- While it says "Type the ESC key to interrup" press the ESC key.
- Type
disable-security
and enter. The XO will reboot automatically. - Again, while it says "Type the ESC key.." press the ESC key.
- Type for a second time
disable-security
and enter. The XO will reboot automatically - 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.
- Plug the key while the XO is off, and turn it on
- 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.
- Plug the key while the XO is off, and turn it on
- It will install the activities and turn off automatically
- 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
- Plug the stick in a turned off XO and turn it on.
- The key will execute the
action
script located in the root directory. You can edit it accordingly. - The
rc.local
file includes code to be executed at boot. - The current action key will copy in the XO several scripts that can be useful in testing, but you can edit at will.