Difference between revisions of "Supported systems"
(add Dextrose) |
(add Harmonic Distribution) |
||
Line 9: | Line 9: | ||
* '''Install Sugar''' | * '''Install Sugar''' | ||
*: If you are running one of the currently supported distributions, you can install Sugar using your systems standard package manager, e.g., Synaptic, apt-get, or yum. See [[Fedora#Sugar_Learning_Environment|these instructions]]. | *: If you are running one of the currently supported distributions, you can install Sugar using your systems standard package manager, e.g., Synaptic, apt-get, or yum. See [[Fedora#Sugar_Learning_Environment|these instructions]]. | ||
+ | *: The [[Platform Team/Harmonic Distribution|Harmonic Distribution]] of the Sugar Learning Platform may also appeal to you. | ||
* '''Install an emulator or virtualizer and launch a bootable Sugar disk image file''' | * '''Install an emulator or virtualizer and launch a bootable Sugar disk image file''' | ||
*: [[QEMU]], [[VirtualBox]], or [[VMware]] let you run Sugar in an emulator or by virtualization on your computer—you'll need to install an emulator from which you launch Sugar and one of the [[Emulator image files]]. | *: [[QEMU]], [[VirtualBox]], or [[VMware]] let you run Sugar in an emulator or by virtualization on your computer—you'll need to install an emulator from which you launch Sugar and one of the [[Emulator image files]]. |
Revision as of 10:50, 7 July 2012
Ways to run Sugar
Determine which of the various methods of running Sugar meet your needs:
- Run Sugar pre-installed in a computer
- Some computers come with Sugar pre-installed, most notably the OLPC XO laptops.
- Some deployments use the Dextrose distribution of Sugar.
- Boot a Live CD / Live USB pre-installed with Sugar
- Suitable for trying Sugar without having to install any software on almost any computer—just boot Sugar off of a CD or USB drive. Note: When booting a Live CD, the Journal is not automatically saved on shutdown, because the boot media is readonly. All changes are lost upon shutdown or reboot. This is not a limitation for Live USB installations. See our Sugar on a Stick project page or other Live USB projects.
- Install Sugar
- If you are running one of the currently supported distributions, you can install Sugar using your systems standard package manager, e.g., Synaptic, apt-get, or yum. See these instructions.
- The Harmonic Distribution of the Sugar Learning Platform may also appeal to you.
- Install an emulator or virtualizer and launch a bootable Sugar disk image file
- QEMU, VirtualBox, or VMware let you run Sugar in an emulator or by virtualization on your computer—you'll need to install an emulator from which you launch Sugar and one of the Emulator image files.
Supported distributions
Sugar is supported by several GNU/Linux distributions. Sugar Labs does not support any specific distribution, but does focus development on Fedora and Debian, which helps SoaS and Ubuntu.
Logo | Name | Notes |
---|---|---|
Sugar on a Stick | Live system of the Sugar Learning Environment | |
Fedora | Fedora 34 | |
Ubuntu | Ubuntu 18.04 Bionic | |
Debian | Debian Stretch, see also Live Build | |
OLPC OS 16.04 | OLPC OS for OLPC NL3 laptops based on Ubuntu 16.04 Xenial | |
OLPC OS 13.x | OLPC OS for OLPC XO laptops based on Fedora 18 | |
openSUSE | Part of an Linux for Education (Li-f-e) series | |
Trisquel Toast | Based on Ubuntu |
Matrix of Sugar solutions
There are many ways to run Sugar:
- As a complete disk image on an existing machine;
- As a session on a Linux system; or
- As part of a complete hardware-software platform.
Technical considerations
- A discussion of technical considerations regarding supported systems.
Sugar for various hardware systems
MacBook Air
OSX 10.6.6 (Virtualbox 4.0.2)Emulator_image_files#VirtualBox VirtualBox runs on most hardware and OS's
Works well in VirtualBox including wireless and magic mouse
Burned Soas.iso for Soas-v4 and Soas-v3 boot fine
Downloads#Apple_Mac_OS_X Apple Mac OS X
Macintosh
Getting the Sugar sources
Distributors can find the latest sources for the sucrose components here. Each release page has as links to the release pages of earlier releases.
Updating Sugar to the Latest Version
Looking at Sugar variants
See Sugar System Stack for a picture of the software stack.
Starch
Starch is a complete disk image for Sugar.
Sucrose
Sucrose is the Sugar interface plus a set of demonstration activities. System maintainers should visit the Packaging Team page.
Old content
Ubuntu
- UbuntuSugarRemix and 10.04LTS
- UbuntuSugarRemix
The Sugar packages in Ubuntu 9.04 and 8.10 Ubuntu#Using_sugar_PPAs.
For a LiveCD/LiveUSB, check out the instructions [1].(Note that this produces a very old sugar version 0.82.1)
Updated sucrose packages are usually published in a PPA: See here for details.
If you want up-to-the-minute freshness (and brokenness) you can use jhbuild to build from source instead of the released packages. Follow the instructions here to install sugar-jhbuild as an xsession option.
Fedora
Fedora LiveCD/Live USB
- Project page: http://fedoraproject.org/wiki/Sugar (superseding: http://fedoraproject.org/wiki/Sugar_Spin)
With this spin, you'll be able to run Sugar, which is developed by Sugarlabs and the desktop environment used on the OLPC, directly from a Live CD! You'll find several activities on the image including most notably...
- sugar-browse - a web browsing activity based on xulrunner
- sugar-write - a word processor based on abiword
...along with several other activities including Chat support.
- See our Sugar on a Stick page.
The Fedora OLPC SIG, https://fedoraproject.org/wiki/OLPC, will be importing further activities into Fedora, which might be installed using yum install sugar-* at a later time.
- Recent development spins:
For more information, please refer to the announcement here:
https://www.redhat.com/archives/fedora-olpc-list/2008-December/msg00061.html
Fedora 11 Preview contains USB Creator which can make USB and SD's with persistence of Fedora F11 (and Sugar if added with Synaptic) and Soas-beta's [satellit 04/30/2009]
What if you wanted to put it quickly onto your USB Key? You'll just need to grab Luke Macken's liveusb-creator, which already includes support for the Sugar Spin. Here's the link:
The liveusb-creator still contains an old link, which is the reason why you'll need to download the spin manually until this gets fixed.
Tip of the hat: Sebastian Dziallas and the Fedora team
Fedora on an OLPC XO
On an OLPC XO-1 laptop, run olpc-update as root.
Normally you only need to run olpc-update in the Terminal application with a build number, like this:
# sudo olpc-update 767
Note: Now you can do this by means of the graphical Sugar Control Panel.
Joyride
See OLPC:Future releases, the Joyride train is in the round house.
Joyride is for developers; it is not supported. Joyride builds may cause data corruption and in rare cases, even cause hardware damage, so please do not use Joyride on mission-critical systems.
Joyride contains all the "bleeding-edge" features that are being debugged for inclusion in the next release.
Open the Terminal application and type the following, substituting 2469 for the latest version number.
# olpc-update joyride-2469
What's the latest version? You can find the latest build number (shown above as 1779) at the bottom of http://xs-dev.laptop.org/~cscott/xo-1/streams/joyride/
Updates usually takes 10–15 minutes. It's advised that you plug your XO in while Sugar updates itself, then reboot it to see the new OS take effect.
Other Options
These are options that can be used with the update command:
# olpc-update --help
Usage: olpc-update [options] --hints hints-file olpc-update [options] [-rf] build-number olpc-update [options] [-rf] --usb olpc-update --version olpc-update --help For example: olpc-update 630 olpc-update joyride-1779 olpc-update update.1-700 Options: -h, --help show this help message and exit -f, --full skip incremental update attempt. --force force update to an unsigned build. -r, --reboot reboot after a successful update. --hints=FILE name of json-encoded hints dictionary identifying the desired new version. -u, --usb upgrade from new build on inserted USB stick. -v display verbose progress information; repeat for more verbose output. -q, --quiet don't output anything; use exit status to indicate success. --version display version and license information.