OS images: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (→‎Build names and branches: link to Builds category)
No edit summary
 
(74 intermediate revisions by 16 users not shown)
Line 1: Line 1:
{{Translations}}
{{Translations}}
{{OLPC}}
'''To emulate the OLPC environment on your Windows, Mac, or Linux machine''', see [[Emulating the XO]].
{{ Latest Releases
{{ Latest Releases
| rc = inline
| rc = inline
Line 8: Line 6:
| livecd = inline
| livecd = inline
| firmware = inline
| firmware = inline
| extra = inline }}
| server = inline }}


OLPC produces '''OS images''' (also known as '''software builds''') which can be installed on XO laptops, customized and rebuilt by deployments, etc. These images include all of the system and user software, allowing your XO to boot straight into OLPC's software environment.
== Definition ==


* To install a specific build on your laptop, follow the links to one of the XO releases from the box on the right. For other releases, see [[Releases]].
OLPC and Red Hat continually develop the Fedora-derived OLPC Linux operating system. Each day, we freeze the most up-to-date version of that OS, and make it available for download as an OS image.
* The [[Release notes]] for each release have instructions for installing or upgrading to a release on your XO. The [[Updating the XO]] page references other ways that software images can be installed.

* If you want to identify which build/release is running on your XO, see [[What release am I running?]].
=== Upgrades ===
* If you are interested in testing upcoming releases, the [[Friends in testing]] page explains where you can start.

* If you know what you're doing, you might be able to find the files that you're looking for on http://download.laptop.org
The recommended method to update your development board or BTest system, is [[Autoreinstallation image]]. Please see that and then return here if you want a different image.
* To build your own image, see [[Building custom images]].

=== Downloads ===

As the operating system for OLPC is under development, there are several builds available. The latest build might not always be stable since developers are experimenting with new features. Each build is labeled with a unique version number. When reporting problems on mailing lists, please make sure you list the build number you are using.

"Update-1" images include selected improvements from the less-stable "joyride" branch. You can get them from

http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/

You can download other recent and stable images from:

http://xs-dev.laptop.org/~cscott/olpc/streams (look in "latest")

And historical ones from:

http://olpc.download.redhat.com/olpc/streams/development

=== Latest Stable Build ===

A build is marked "stable" when the developers are happy with it. At minimum, it should boot successfully on A-Test boards and B-Test laptops. A stable build does not mean everything is working, nor that it is actually "stable." For example, for a while [[Sugar]] and X were both broken in a stable build, but virtual consoles worked fine and that was enough to get work done for most developers.

Casual downloaders and those upgrading to a new build beware: '''check the [http://dev.laptop.org/tinderbox/ Tinderbox] to see whether there are known problems before selecting a build'''.

The latest stable build is the highest-numbered build at [http://download.laptop.org/xo-1/os/official].

== Image variants ==

Images are available in five variants

* Normal images in the <tt>ext3/</tt> and <tt>jffs2/</tt> sub-directories
** Intended for production use
** Does not contain tools or software suitable for developers of the OLPC operating system
** The <tt>ext3/</tt> images are intended for USB drives (both hard drives and flash drives)
** The <tt>jffs2/</tt> images are intended for the on-board NAND flash.

* Developer images in the <tt>devel_ext3/</tt> and <tt>devel_jffs2/</tt> sub-directories
** Contains tools useful for developers of the OLPC operating system, including: <tt>yum, rpm, vim-minimal, openssh-server, xterm, which, file, tree, wget, xorg-x11-twm, gdb</tt> packages
** The <tt>devel_ext3/</tt> images are intended for USB drives (both hard drives and flash drives)
** The <tt>devel_jffs2/</tt> images are intended for the on-board NAND flash
** '''WARNING''': Do not attempt to update the kernel on <tt>devel_*</tt> builds - the <tt>initrd</tt> will be wrong. We're working on fixing this through including an <tt>olpc-mkinitrd</tt> package.

* Live CD images in the <tt>livecd/</tt> sub-directory
** Contains an iso of a normal image which can be burned onto a cd and run by booting off the cd drive

Each variant may have available two sub-variants:

* tree: a tarball of the OS directory tree, without a filesystem
* img: a filesystem image (of one of the types described above).

== Languages in which the images are available ==

* English
* The home Language for each participating country

== Using Images ==

For development we offer images that run the OLPC operating system off a USB storage device. These images are located in the <tt>devel_ext3/</tt> sub-directory, and should be used if you're unsure of which image to choose.

=== Passwords ===

Some recent builds do not permit root login. There are quite a few tickets. You can login as ''olpc'', no password, and <tt>sudo -i</tt> instead. [[User:MitchellNCharity|MitchellNCharity]] 14:40, 6 January 2008 (EST)

The images have no password set at build time. This means you can log in as root using no password. Always remember to change the password as the first thing when start using an image.

As the <tt>image-rpm</tt> variant ships with an SSH server you thus need to set the password to be able to login from a remote host. This is a feature of <tt>sshd</tt>.

''Password handling is subject to change before official release.''

=== Images on a USB disk ===

The '''[[OS images for USB disks]]''' page describes how to write these images to a USB disk, so that you can test the images on real OLPC hardware, or attempt to boot from them on your own PC.

=== Images on an emulator ===

The '''[[OS images for emulation]]''' page details how you can run an image of the OLPC operating system on a normal computer that doesn't have the OLPC hardware.

=== Images with the on-board NAND flash on OLPC hardware ===

See the [[Autoreinstallation image]] page.

=== Wireless ===

See the [[Wireless]] page for detailed instructions.

== Test Group Release Notes for Images ==

The [[Test Group Release Notes]] page lists the "official" changelog and known problems for each build. Check that page to see if there are any known problems with the build you're installing.

== User Feedback on Images ==

Using the [[User Feedback on Images]] page, you can see how the images worked on various systems, using various different hardware and emulator set-ups. You can also add your own reviews.

== Build names and branches ==
''(from 2007-12-04 [http://lists.laptop.org/pipermail/devel/2007-December/008138.html mailing list message] by Chris Ball:)
; Ship.1 is build623, and was preloaded on all mass production XO machines for a while.
: It isn't preloaded on new machines, and any machine with it installed should since have been updated to Ship.2. It was released around 2007-11-01. It will mostly not be seen by the outside world at all.

; Ship.2 is build650
: It is the build received by [[Give One Get One]] recipients, as well as the [[OLPC Uruguay|Uruguay Ceibal project]] users. (Actually, Uruguay is using a slightly custom build, but it's based on Ship.2.) It was released around 2007-12-01.

; Update.1 is not released, and as of December 2007 being worked on in the "joyride" branch.
: After code freeze, scheduled for around 2007-12-15, a copy of the joyride branch will be made and named update.1, and any development that isn't targeting Update.1 can continue in joyride. Update.1 release is scheduled for mid January, as seen on the [http://dev.laptop.org/roadmap roadmap].
: The roadmap also contains the feature goals for Update.1. Machines can be automatically upgraded (preserving user data) from Ship.2 to Update.1 after release.

; Joyride
: Can be thought of as synonymous with "trunk" or "HEAD" or "unstable", much like the Debian/unstable distribution.

'''Patches'''<br>
Please see the [[Operating_system_release_procedures]] for information on the patch release process.

Here is a list of the patches to date:

* [[OLPC 653 Software Release Notes]] - Ship2 patch1, 653
* [[OLPC 656 Software Release Notes]] ([[OLPC SW-ECO 2]]) - Ship2 patch2, 656

See [[:Category:Builds]] for other wiki pages related to builds and releases.

== Building your own custom images ==

See [[Building custom images]]


[[Category:Hardware]]
[[Category:Hardware]]
Line 142: Line 21:
[[Category:OS]]
[[Category:OS]]
[[Category:Build system]]
[[Category:Build system]]
[[Category:Update paths]]
[[Category:Builds]]

Latest revision as of 21:51, 5 August 2013

  english | 日本語 HowTo [ID# 290705]  +/-  



OLPC produces OS images (also known as software builds) which can be installed on XO laptops, customized and rebuilt by deployments, etc. These images include all of the system and user software, allowing your XO to boot straight into OLPC's software environment.

  • To install a specific build on your laptop, follow the links to one of the XO releases from the box on the right. For other releases, see Releases.
  • The Release notes for each release have instructions for installing or upgrading to a release on your XO. The Updating the XO page references other ways that software images can be installed.
  • If you want to identify which build/release is running on your XO, see What release am I running?.
  • If you are interested in testing upcoming releases, the Friends in testing page explains where you can start.
  • If you know what you're doing, you might be able to find the files that you're looking for on http://download.laptop.org
  • To build your own image, see Building custom images.