Changes

<noinclude>{{TOCright}}</noinclude>

<noinclude>{{TOCright}}</noinclude>

== Introduction ==

== Introduction ==

For a more stable, released version of Sugar on a Stick, see '''[[Sugar_on_a_Stick/Strawberry#Linux_Users | v1 Strawberry]]'''.

This page provides additional detail for installing the most stable, released version of Sugar on a Stick (SoaS), '''[[Sugar_on_a_Stick/Strawberry#Linux_Users | v1 Strawberry]]''' on a USB flash storage device using GNU/Linux.

To explore a variety of '''experimental''' options for putting a [[Sugar on a Stick]] image on a USB flash drive under GNU/Linux, see the following pages:

: To explore a variety of '''experimental''' options for putting a [[Sugar on a Stick]] image on a USB flash drive under GNU/Linux, see the following pages:

[[Sugar on a Stick/Beta]] | [[Sugar on a Stick/Installation/OLPC|OLPC XO-1]] | [[Sugar on a Stick/Linux/openSUSE|openSUSE]] | [[Trisquel On A Sugar Toast|Trisquel]] | [[VirtualBox]] | [[VMware]]

: [[Sugar on a Stick/Beta|SoaS v2 test builds]] | [[Sugar on a Stick/Installation/OLPC|OLPC XO-1]] | [[Sugar on a Stick/Linux/openSUSE|openSUSE]] | [[Trisquel On A Sugar Toast|Trisquel]] | [[VirtualBox]] | [[VMware]] | [[Sugar on a Stick/Linux/Non-compressed Fedora|non-compressed Fedora]]

If you have questions, trouble, or feedback, please let us know on the [[{{TALKPAGENAMEE}}|discussion]] page. "Sugar on a Stick" is provided in a number of [[Talk:Sugar_on_a_Stick/Linux#SoaS_Fedora_matrix|variants]]. If you can improve these instructions, please edit the page and do so!

If you have questions, trouble, or feedback, please let us know on the [[{{TALKPAGENAMEE}}|discussion]] page. If you can improve these instructions, please edit the page and do so!

== Put SoaS onto a stick using Fedora or Ubuntu ==

== Put SoaS onto a stick using Fedora or Ubuntu ==

This is known to work in Fedora and Ubuntu.

This is known to work in Fedora and Ubuntu.

First, start downloading a SoaS <tt>.iso</tt> image from the [[Sugar on a Stick#Download locations|download locations section]], then return here.

First, start downloading a SoaS <tt>.iso</tt> image from the [[Sugar on a Stick/Strawberry#Download locations|download locations section]], then return here.

:(A program called UNetBootin available at http://unetbootin.sourceforge.net/ does all this magic for you... or you can do the magic yourself:)

::<small>(A program called UNetBootin available at http://unetbootin.sourceforge.net/ does all this magic for you... or you can do the magic yourself:)</small>

* Make sure you have the ''syslinux'' package installed on the operating system that you will use to prepare the Live USB image. It is recommended that you also have the ''isomd5sum'' package installed. The ''cryptsetup'' package is another option potentially used by the "livecd-iso-to-disk" installation script. (On Ubuntu, <code>sudo apt-get install syslinux isomd5sum cryptsetup</code> will install the packages. They are also available through the Synaptic Package Manager.)

* Make sure you have the ''syslinux'' package installed on the operating system that you will use to prepare the Live USB image. It is recommended that you also have the ''isomd5sum'' package installed. The ''cryptsetup'' package is another option potentially used by the "livecd-iso-to-disk" installation script. (On Ubuntu, <code>sudo apt-get install syslinux isomd5sum cryptsetup</code> will install the packages. They are also available through the Synaptic Package Manager.)

: (On Gentoo, one needs to uncomment 'SAMPLE FILE' in /etc/mtools/mtools.conf to make syslinux work.)

:: <small>(On Gentoo, one needs to uncomment 'SAMPLE FILE' in /etc/mtools/mtools.conf to make syslinux work.)</small>

:*''syslinux'' is needed to set up booting on the FAT file system of the USB disc or Live CD.

:*''[[wikipedia:Syslinux|syslinux]]'' is needed to set up booting on the FAT file system of the USB disc or Live CD.

:*''isomd5sum'' is needed for the recommended verification step, which checks that the .iso file is complete after its travels. If there is a problem with the .iso file, the script will exit and provide a failure message.  The verification step can be bypassed by using the <code>--noverify</code> option.

:*''[[wikipedia:md5sum|isomd5sum]]'' is needed for the recommended verification step, which checks that the .iso file is complete after its travels. If there is a problem with the .iso file, the script will exit and provide a failure message.  The verification step can be bypassed by using the <code>--noverify</code> option.

:*''cryptsetup'' is only needed for the option to provide password protection and encryption for the persistent /home/liveuser folder. It is not necessary if one applies the  recommended <code>--unencrypted-home</code> option. The <code>--unencrypted-home</code> option is preferred because the reduced overhead improves robustness with the compressed ''squashfs'' file system employed by the Live USB deployment.

:*''[[wikipedia:dm-crypt|cryptsetup]]'' is only needed for the option to provide password protection and encryption for the persistent /home/liveuser folder. It is not necessary if one applies the  recommended <code>--unencrypted-home</code> option. The <code>--unencrypted-home</code> option is preferred because the reduced overhead improves robustness with the compressed ''[[wikipedia:SquashFS|SquashFS]]'' file system employed by the Live USB deployment.

* Plug in a 1GB or larger USB stick into your computer.

* Plug in a 1-GB or larger USB stick into your computer.

* Download the installation script: http://download.sugarlabs.org/soas/releases/livecd-iso-to-disk.sh (23 June 2009).<br>(You will execute this script several steps below.)

* Download the installation script: http://download.sugarlabs.org/soas/releases/livecd-iso-to-disk.sh (23 June 2009).<br>(You will execute this script several steps below.)

* Check the USB device name. In the example below, the '''s'''torage '''d'''evice is /dev/sdb and filesystem partition on that device is /dev/sdb1:

* Check the USB device name. In the example below, the '''s'''torage '''d'''evice is /dev/sdb and filesystem partition on that device is /dev/sdb1:

::# quit  

::# quit  

* Change mode to make the script executable.  

* Change mode to make the script executable.  

: <tt>chmod +x livecd-iso-to-disk.sh</tt>

: <tt>chmod +x livecd-iso-to-disk.sh</tt>

::* The <code>--delete-home</code> option is used to avoid an error message while requesting both a new home (with <code>--home-size-mb</code>) and a persistent home (indirectly with <code>--unencrypted-home</code>). You wouldn't use the --delete-home option on an upgrade of the operation system only.

::* The <code>--delete-home</code> option is used to avoid an error message while requesting both a new home (with <code>--home-size-mb</code>) and a persistent home (indirectly with <code>--unencrypted-home</code>). You wouldn't use the --delete-home option on an upgrade of the operation system only.

:Depending on the size of your USB stick, you may have to decrease <code>--overlay-size-mb</code> and <code>--home-size-mb</code> values (for example, for a 1-GB stick, use 200 for each).

:Depending on the size of your USB stick, you may have to decrease <code>--overlay-size-mb</code> and <code>--home-size-mb</code> values (for example, for a 1-GB stick, use 200 for each).

:* If you get an error about udevinfo, you have the new version of udev where "udevadm info" is the proper command. :Create an executable file called udevinfo somewhere in your path with the following contents:

:* If you get an error about udevinfo, you have the new version of udev where "udevadm info" is the proper command.

:*:Create an executable file called udevinfo somewhere in your path with the following contents:

:::<code>#!/bin/bash</code><br>

:::<code>#!/bin/bash</code><br>

:::<code>udevadm info $*</code>

:::<code>udevadm info $*</code>