Difference between revisions of "Talk:Sugar on a Stick/Linux"

From Sugar Labs
Jump to navigation Jump to search
m (→‎SoaS Fedora matrix: update to soas03)
Line 49: Line 49:
 
'''No this page is not about how to put an .iso on a removable drive, but how to run sugar-desktop on removable USB/SD drives in Linux.'''
 
'''No this page is not about how to put an .iso on a removable drive, but how to run sugar-desktop on removable USB/SD drives in Linux.'''
 
The openSUSE version is a .raw image that is burned to a stick by the dd command. It creates a usb stick that boots sugar-desktop with 55 applications. It is a valid way to access sugar and its applications. I personally think that it belongs here. [satellit 08/02/2009]
 
The openSUSE version is a .raw image that is burned to a stick by the dd command. It creates a usb stick that boots sugar-desktop with 55 applications. It is a valid way to access sugar and its applications. I personally think that it belongs here. [satellit 08/02/2009]
 +
 +
== Page restructure needed==
 +
 +
Let us please use this SoaS/Linux page primarily to provide background support for the installation of the stable SoaS release reported on the main SoaS page, and provide links to sub pages for all the other distributions and experimental and exploratory variations.
 +
 +
This page would be more valuable if it provided more easy to follow detail and explanations for the Linux installation steps and an index to the other options advanced users or developers might want to investigate.

Revision as of 21:32, 28 October 2009

SoaS Fedora matrix

SoaS
version
Release
name
OS
version
disc image files
alpha -- Fedora 10 (unavailable as of 04 October 2009)
alpha, beta -- Fedora 11 http://download.sugarlabs.org/soas/snapshots/1/
beta -- Fedora 11 http://download.sugarlabs.org/soas/releases/soas-1-beta.iso
v1 Strawberry Fedora 11 http://download.sugarlabs.org/soas/releases/soas-1-strawberry.iso
v2 alpha, beta -- Fedora 12 http://download.sugarlabs.org/soas/snapshots/2/
(includes builds for the XO-1 hardware)
soas03 -- Fedora 12 http://download2.sugarlabs.org/soas/snapshots/2/soas03.iso
v2 Blueberry Fedora 12
  • The snapshots subfolder number now matches the release lineage version number. Before 04 October 2009 it referred to the Fedora version since the original SoaS (1 = Fedora 10, 2 = Fedora 11, 3 = Fedora 12), but the subfolders have be repurposed (the older filenames, e.g., Soas2-YYYYMMDDHHMM.iso, still bear the original series number code).
  • Beginning on 04 October 2009, SoaS and SoaS-XO-1 images share the same codebase. Image filesnames follow a simple numbering scheme beginning with soas01.* for Sugar on a Stick and soasxo01.* for that codebase with the X0-1-specific kernel.

Remove openSuSE section?

I haven't wanted to remove the openSuSE section because I'm loathe to start another flamewar, but it seems out of place: the page says "This page helps you to put your Sugar on a Stick image on a USB flash drive under Linux.", but the openSuSE section isn't about this. The openSuSE SoaS image is already on the Sugar on a Stick page along with all the other images.

As the openSuSE section is not about how to put a .iso onto a removable drive, does anyone object to it being removed?

No this page is not about how to put an .iso on a removable drive, but how to run sugar-desktop on removable USB/SD drives in Linux. The openSUSE version is a .raw image that is burned to a stick by the dd command. It creates a usb stick that boots sugar-desktop with 55 applications. It is a valid way to access sugar and its applications. I personally think that it belongs here. [satellit 08/02/2009]

Page restructure needed

Let us please use this SoaS/Linux page primarily to provide background support for the installation of the stable SoaS release reported on the main SoaS page, and provide links to sub pages for all the other distributions and experimental and exploratory variations.

This page would be more valuable if it provided more easy to follow detail and explanations for the Linux installation steps and an index to the other options advanced users or developers might want to investigate.