Testing Update.1: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (14 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
{{archive}} |
|||
As of build candidate-699, activities are no longer bundled with the core build -- they must be installed separately. This page attempts to describe the motivation for the change, and how to get your activities back. |
As of build '''candidate-699''', activities are no longer bundled with the core build -- they must be installed separately. This page attempts to describe the motivation for the change, and how to get your activities back. |
||
== Motivation == |
== Motivation == |
||
OLPC has many deployments, as well as the G1G1 user community, and can't afford to create a build for each deployment. Instead, OLPC will create a "core build" without activities that allows for easy customization of which resources (activities, content bundles) will be installed alongside it. The mechanism for performing this customization is the [[Customization key]]. |
OLPC has many deployments, as well as the G1G1 user community, and can't afford to create a build for each deployment. Instead, OLPC will create a "core build" without activities that allows for easy customization of which resources (activities, content bundles) will be installed alongside it. The mechanism for performing this customization is the [[Customization key]]. We will create single step upgrade/customization capabilities as soon as possible to make this even easier for the end user. |
||
== I ran olpc-update to an update.1 build; how do I get my activities back? == |
== I ran olpc-update to an update.1 build; how do I get my activities back? == |
||
Download the [[G1G1 Activity Pack]] and install it from a USB flash drive. |
|||
You can download the [[G1G1_Activity_Pack]], unzip it onto a USB key, and reboot with the X game key held down. Linux will boot and unpack each of the bundles into place. |
|||
== What's the recommended way to upgrade? == |
== What's the recommended way to upgrade? == |
||
See the [[OLPC_Update.1_Software_Release_Notes#What.27s_the_recommended_way_to_upgrade.3F|corresponding section]] in the [[OLPC Update.1 Software Release Notes|Update.1 release notes]]. |
|||
| ⚫ | |||
The recommended method is to run [[Olpc-update]] to the new build, and then to reboot with a [[G1G1_Activity_Pack]] key inserted. |
|||
| ⚫ | |||
"Secure" machines without developer keys will boot a customization key at startup without any intervention. "Insecure" machines with a developer key installed require the X game key to be held at boot to boot a customization key. |
"Secure" machines without developer keys will boot a customization key at startup without any intervention. "Insecure" machines with a developer key installed require the X game key to be held at boot to boot a customization key. |
||
| Line 19: | Line 18: | ||
== Which builds are signed, and why does it matter? == |
== Which builds are signed, and why does it matter? == |
||
There are three streams for update.1 builds -- "update.1", "candidate", and "release". The first |
There are three streams for update.1 builds -- "update.1", "candidate", and "release". The first is unsigned, the latter two are signed. The workflow is: |
||
* Update.1 builds are created (for example, "update.1-699"), and if they pass testing such that they're an improvement over previous candidates, they become a signed "candidate" build. |
* Update.1 builds are created (for example, "update.1-699"), and if they pass testing such that they're an improvement over previous candidates, they become a signed "candidate" build. |
||
* Candidate builds are represented in the form "candidate-699", and are our latest proposed final build for a release. |
* Candidate builds are represented in the form "candidate-699", and are our latest proposed final build for a release. |
||
* Release builds are builds that have been passed to Quanta for installation on new laptops. Notwithstanding an [ |
* Release builds are builds that have been passed to Quanta for installation on new laptops. Notwithstanding an [[Unscheduled_software_release_process|Unscheduled software release]], we expect only one of these builds per release cycle. |
||
== Creating your own activity pack == |
== Creating your own activity pack == |
||
(See corresponding section in [[Activity pack]].) |
|||
The [http://dev.laptop.org/~cjb/create-customization-key create-customization-key] Python script will create a customization key for G1G1 (or Mexico, or Peru, or "all"). You should first unpack a customization key image on to a USB disk, and then in the root of the USB disk: |
|||
== See also == |
|||
* The final location of the list of default activities, will appear in : |
|||
/usr/share/sugar/data/activities.default |
|||
* Other developing activity packs. |
|||
** [[G1G1 Activity Pack]] or [[G1G1 activity pack]]. |
|||
** [[Peru activity pack]] |
|||
* Another future option for installing 'activity pack' bundles, from console use [[xo-get]]. |
|||
<pre>python create-customization-key G1G1</pre> |
|||
[[Category:Testing]] |
|||
Latest revision as of 04:00, 22 August 2008
As of build candidate-699, activities are no longer bundled with the core build -- they must be installed separately. This page attempts to describe the motivation for the change, and how to get your activities back.
Motivation
OLPC has many deployments, as well as the G1G1 user community, and can't afford to create a build for each deployment. Instead, OLPC will create a "core build" without activities that allows for easy customization of which resources (activities, content bundles) will be installed alongside it. The mechanism for performing this customization is the Customization key. We will create single step upgrade/customization capabilities as soon as possible to make this even easier for the end user.
I ran olpc-update to an update.1 build; how do I get my activities back?
Download the G1G1 Activity Pack and install it from a USB flash drive.
What's the recommended way to upgrade?
See the corresponding section in the Update.1 release notes.
Upgrading a secure/insecure machine
"Secure" machines without developer keys will boot a customization key at startup without any intervention. "Insecure" machines with a developer key installed require the X game key to be held at boot to boot a customization key.
Which builds are signed, and why does it matter?
There are three streams for update.1 builds -- "update.1", "candidate", and "release". The first is unsigned, the latter two are signed. The workflow is:
- Update.1 builds are created (for example, "update.1-699"), and if they pass testing such that they're an improvement over previous candidates, they become a signed "candidate" build.
- Candidate builds are represented in the form "candidate-699", and are our latest proposed final build for a release.
- Release builds are builds that have been passed to Quanta for installation on new laptops. Notwithstanding an Unscheduled software release, we expect only one of these builds per release cycle.
Creating your own activity pack
(See corresponding section in Activity pack.)
See also
- The final location of the list of default activities, will appear in :
/usr/share/sugar/data/activities.default
- Other developing activity packs.
- Another future option for installing 'activity pack' bundles, from console use xo-get.