Update streams: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (Shorter title)
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Current releases of OLPC OS do not use update streams using the method detailed below. [[13.2.5]] and later do automatically update activities, and this is a feature of Sugar.
The XO contacts OLPC on average once a day in order to see if there is a new build which it should be running. Each XO can be subscribed to one of a number of "update streams":

Deployment builds of OLPS OS can be configured to contact OLPC on average once a day in order to see if there is a new build which it should be running. Each XO can be subscribed to one of a number of "update streams":
* none - never update me.
* none - never update me.
* stable - latest stable build
* stable - latest stable build
Line 5: Line 7:
* joyride - not yet implemented, but will someday give you the latest joyride build automatically.
* joyride - not yet implemented, but will someday give you the latest joyride build automatically.


{{Activation.laptop.org}}
See https://activation.laptop.org/streams/ for the full list.


See https://activation.laptop.org/streams/ for the full list.
The stream an XO is subscribed to is determined as follows:
The stream an XO is subscribed to is determined as follows:
# If there is a file named '''/security/update-stream''' containing a stream name, use it.
# If there is a file named '''/security/update-stream''' containing a stream name, use it.
Line 14: Line 17:


== Automatic update prevention ==
== Automatic update prevention ==
Start the [[Terminal Activity]] and become the [[root]] user, then at the <tt>#</tt> prompt type
In a root shell:
# echo none > '''/security/update-stream'''
echo none > '''/security/update-stream'''
then press the Enter key.

[[Category:Update paths]]

Latest revision as of 01:27, 17 November 2015

Current releases of OLPC OS do not use update streams using the method detailed below. 13.2.5 and later do automatically update activities, and this is a feature of Sugar.

Deployment builds of OLPS OS can be configured to contact OLPC on average once a day in order to see if there is a new build which it should be running. Each XO can be subscribed to one of a number of "update streams":

  • none - never update me.
  • stable - latest stable build
  • testing - release candidates or stable upgrade testing
  • joyride - not yet implemented, but will someday give you the latest joyride build automatically.
activation.laptop.org
has been turned off,
if this hinders you,
read more about it.

See https://activation.laptop.org/streams/ for the full list. The stream an XO is subscribed to is determined as follows:

  1. If there is a file named /security/update-stream containing a stream name, use it.
  2. Otherwise, if there is a file named /etc/olpc-update/update-stream with a stream name, use this. (This is used in joyride builds to ensure the joyride machines are by default subscribed to joyride, not stable.)
  3. Otherwise, if the laptop belongs to an 'update group' in OLPC's database, and the update group names a default stream, use it. (This allows us to remotely upgrade XOs in school deployments.)
  4. Otherwise, use the default update stream specified by the server, which is currently 'stable'.

Automatic update prevention

Start the Terminal Activity and become the root user, then at the # prompt type

echo none > /security/update-stream

then press the Enter key.