Sugar on a Stick/Beta

Soas05 Beta

• (Fedora 12 beta (rawhide)) See Soas Fedora image matrix.

Download

• Sugar on a Stick v2 snapshots are available for download at http://download2.sugarlabs.org/soas/snapshots/2/, latest test version, soas05.iso (updated 11 Nov 2009).

SoaS Installation on USB/SD

• Use ONLY this script file to create a bootable image, http://bit.ly/livecd-iso-to-disk.

(Don't forget to chmod +x tools_livecd-iso-to-disk.sh after you download the script.)

• The .iso file may be burnt to a CD-ROM and booted on your PC (or mounted in a virtual machine to boot it):

Note:

• See this announcement for more information.
• To install the .iso disc image, execute the shell script as the root user in one command with arguments as follows:

sudo ./tools_livecd-iso-to-disk.sh --overlay-size-mb 400 --delete-home --extra-kernel-args selinux=0 ./soas05.iso /dev/sd*1

• (*) be sure of your USB/SD storage device name (such as sda, sdb, etc.) and partition (such as 1, 2, etc.), yielding, for example, /dev/sdb1. Use the mount command or the partition manager to confirm it before executing the script.
• --format --reset-mbr are optional arguments for the shell script, but may be excluded to preserve the existing disc format and data. See olpc:How to Damage a FLASH Storage Device for a discussion of why you might want to try to keep your factory format on a flash storage device.
• If you do use the format and reset master boot record arguments, you'll want to specify the target device name and not a partition, that is /dev/sd* with no partition number, instead of /dev/sd*1 as in the example above used to specify an existing partition. As noted above, confirm your target disc device name—in this case, it is VERY DANGEROUS to your other discs if this is entered wrong, as the whole disc will be reformatted and a new master boot record written causing all previously written data on that disc to be lost.

Alternate 'hybrid-mode' method using dd (not working at present)

An alternate method of creating a LiveUSB stick form of the .iso (a 'hybrid' image) to make a bootable USB/SD (NOT RECOMMENDED)

• If you use dd command to write a USB or SD image, there will be no persistence. The SCRIPT method detailed above should be used.

In Root Terminal:

dd if=soas04.iso of=/dev/sd(?) bs=4M

• Be sure your USB/SD is /dev/sd? check with partition manager to be sure.

CAUTION: ** You can destroy you Hard Disk if you enter it wrong! **

ZyX-LiveInstaller

• ZyX-LiveInstaller allows you to install SoaS when it is already running from either a LiveUSB device or LiveCD media to a system or external disk. This results in what is considered a traditional operating system installation on disk (or USB-Stick/SD-Card). This is unlike the above methods which create a Live Media (USB/SD) from the .iso file.
• It is known to work best with the most recent snapshot build - soas04.iso.[1]

• To use

• start the terminal activity, type in lowercase 'zyx-liveinstaller', then press enter.
• start the partitioner 'gparted' if necessary

• you will need at least a single partition for the root filesystem, that is greater than 2GB. Some disks labeled and sold as 2GB may not be quite large enough.
• optionally, you may use a seperate partition for the /boot filesystem
• optionally, you may select a seperate partition for swap space. 1-2GB is recommended and will allow the use of hibernation (suspend-to-disk)
• note: formatting in the partitioner is not required.
• exit the partitioner by hitting the X in the top corner of window.

• read and follow the simple wizard, choosing destination volumes/partitions for boot, root, and swap. boot may be the same as root, and swap is optional.

• This is a *destructive* install, meaning that the contents of the disks or partitions you choose will be overwritten entirely.
• During installation, you are free to use other activities.
• After installation completes, you may remove the LiveUSB or LiveCD, and continue using the newly installed system - without rebooting!!!. This means that anything done with the system before, during, or after installation persists into the installed system.
• An example with details of install in a virtual machine[2]