Updates will be installed automatically when the OLPC team have tested them thoroughly. For those users that would like to help by reporting bugs, testing fixes and improving the system software, the following information can help you decide if upgrading to a pre-release version of software is right for you.

Most changes made to your XO are reversible and your data will not be at risk of being lost. Where that is not true, it is very clearly stated as being so.

and if you can identify how joyride versions graduate into releasesthat can be installed by number so much the better.

Joyride is the bleeding edge of XO development. Its built from the latest packages the developers make. We try our best to keep it in a semi-working state but often its completely broken.

Joyride autobuilds around every hour or so if there are new packages to pull. Build announcements + changes are e-mailed to the developer list.

Right now a certain subset of Joyride will get moved into our "stable" builds to fix critical issues and bring some of the new features online.

Eventually we will start forking joyride every so often and then just commit bugfixes to that branch but right now its hard to do because Joyride is very different than the Ship.x series.

Some of the new features (like full containerization of activities) are very disruptive. Update.x will bring it closer to Joyride but its going to take a few more releases until we get things where we want them.

I've got two (specifically so that I can experiment with one ofthem), but I don't yet have a good feel for how the various releasesgo together

The best thing you can do to help OLPC is to get a devkey, test Joyride and Update.x (when they happen) builds and report problems.

Updates will be installed automatically when the OLPC team have tested them thoroughly. For those users that would like to help by reporting bugs, testing fixes and improving the system software, the following information can help you decide if upgrading to a pre-release version of software is right for you.

Most changes made to your XO are reversible and your data will not be at risk of being lost. Where that is not true, it is very clearly stated as being so.

I've returned to the forum a few times to see if this question has been answered. The recent post by Peter about updating (in Tips, etc.) seems to contradict what mburns posted below about updates being installed automatically, so I am still unclear as to whether I should install an update using Peter's step-by-step directions or sit tight waiting for the "automatic" update. Thanks for clarifying.GW

[quote="Daniel"]Regarding this line in the post below:

Updates will be installed automatically when the OLPC team have tested them thoroughly.

I'm not clear exactly what that means... Does it mean that one day I will sign onto the internet with my G1G1 and be upgraded to the latest Build without having to do anything at all?

Thanks,Daniel

[quote="mburns"]This thread is a work in progress and is kept up to date by the OLPC Support Gang.

More questions here - I just got my replacement XO, loaded with 650. The front page of the wiki says that 653 is the stable build. The wiki page about updating says that it's 656 in most places, and 653 in at least one at the end

15. Select the "Shutdown" option to power off the machine. Now you should be able to power it up as usual, with build 653.

Does anyone know why the wiki asks us to have the XO plugged into AC power when using olpc-update? Has anyone tried doing it while on battery power? If any of the gang understand the secret sauce a little better than I do I'd appreciate a little enlightenment.

For XO build update I think the AC power requirement is just a safety issue. However, for Firmware update it is a requirement. Loss of power would cause a brick. Maybe OLPC-Update does a firmware update also?

gwallace wrote:I've returned to the forum a few times to see if this question has been answered. The recent post by Peter about updating (in Tips, etc.) seems to contradict what mburns posted below about updates being installed automatically, so I am still unclear as to whether I should install an update using Peter's step-by-step directions or sit tight waiting for the "automatic" update. Thanks for clarifying.

The XO software has automatic software updating as part of the system. XO's phone home every day or so. Once the system is enabled, the XO's will get instructions to update if they need it. The XO will start an olpc-update session and upgrade.

It appears this won't happen until Ship.1 or Update.1 or whatever the name of the next release is going to be called. Of course, anyone can update on demand using the olpc-update command with the release number or using the offline update using a USB Flash drive and the release files.

If you want to install a test version (like any of the development builds) then you need a Developer's Key to disable security. XO's that are secure (as all of the G1G1 laptops) will not accept a non-signed version. The exception to this is if developers release a candidate version they want widespread review they will sign it. The release notes indicate this option.

I'm not clear exactly what that means... Does it mean that one day I will sign onto the internet with my G1G1 and be upgraded to the latest Build without having to do anything at all?

Yes. Unless you opt out of automatic updates. To opt out, open a Terminal activity and enter these commands: