Operating system image installation methods: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 26: Line 26:
| .zd and fs.zip
| .zd and fs.zip
| hold down the four game pad buttons
| hold down the four game pad buttons
| [[F11_for_1.5#Internal_microSD|Fedora 11 for XO-1.5 install to internal microSD]] [[Release_notes/10.1.1]]
|-
|-
| XO-1.5 unsigned
| XO-1.5 unsigned
| .zd alone
| .zd alone
| check if security is disabled, if so obtain developer key and [[Developer_key#Disable_the_security_system|disable-security]], interrupt boot, then use the ''fs-update'' command
| check if security is disabled, if so obtain developer key and [[Developer_key#Disable_the_security_system|disable-security]], interrupt boot, then use the ''fs-update'' command
| [[F11_for_1.5]]
|
|}
|}


Note that signed methods are the same for XO-1 and XO-1.5. Intentional design, since we do not wish to increase the training burden for the deployment teams.
Note that signed installation methods are the same for XO-1 and XO-1.5. Intentional design, since we do not wish to increase the training burden for the deployment teams.

Revision as of 06:55, 24 June 2010

We use a few different methods to install operating system images.

installation method what files are required how to install references
XO-1 signed .img and fs.zip hold down the four game pad buttons Clean Install Procedure
XO-1 unsigned .img and .crc obtain developer key, disable-security, interrupt boot, then use the copy-nand command Clean Install Procedure
XO-1 partitioned
.dat and .img obtain developer key, disable-security, interrupt boot, then use the update-nand command Used by DebXO. Used by UBIFS experiments.

Technical description.

XO-1.5 signed .zd and fs.zip hold down the four game pad buttons Fedora 11 for XO-1.5 install to internal microSD Release_notes/10.1.1
XO-1.5 unsigned .zd alone check if security is disabled, if so obtain developer key and disable-security, interrupt boot, then use the fs-update command F11_for_1.5

Note that signed installation methods are the same for XO-1 and XO-1.5. Intentional design, since we do not wish to increase the training burden for the deployment teams.