Sugar on a Stick/Linux: Difference between revisions

Line 7:

== Linux instructions ==

This is known to work in Fedora and Ubuntu ~~8.10~~ and should work in other Linux distributions.

This is known to work in Fedora and Ubuntu and should work in other Linux distributions.

* Make sure you have the ''isomd5sum'' and ''~~cryptsetup~~'' packages installed in your distribution, as they will be needed by the installation script.

* Make sure you have the ''isomd5sum'', ''cryptsetup'', and ''syslinux'' packages installed in your distribution, as they will be needed by the "livecd-iso-to-disk" installation script. (On Ubuntu, <code>sudo apt-get install isomd5sum cryptsetup syslinux</code> will install the packages.)

*~~:(These packages are~~ needed for the verification ~~and persistent home folder options of~~ the ~~installation~~ script~~; they are not necessary~~ if ~~one applies~~ the <tt>--noverify</tt> and <tt>--unencrypted-home</tt> ~~options, respectively~~. The ~~verification step checks that the file is complete after its travels, and it will signal a failure warning if there is a problem.) The~~ --unencrypted-home option ~~may be~~ preferred ~~for improved~~ robustness with the compressed file system employed by the ~~LiveUSB~~ deployment.

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

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

**''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 <tt>--unencrypted-home</tt> 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.

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

* Download the installation script: http://people.sugarlabs.org/sdz/livecd-iso-to-disk.sh (09 April 2009)

~~:Ensure Ubuntu has the packages required to run the livecd-iso-to-disk.sh~~

~~: <tt>sudo apt-get install isomd5sum cryptsetup syslinux</tt>~~

* Check the USB device. In the example below the device is /dev/sdb:

: <tt>df -h</tt>

Line 62:

Line 63:

* Run it as root, making sure to pass the correct USB device and to set overlay and home size appropriately, depending on the stick size.

: <tt>sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-beta.iso /dev/sdb1</tt>

The ~~Linux~~ installation has the advantage of allowing a persistent /home/liveuser folder with the <tt>--home-size-mb ''NNN''</tt> option. This feature would allow you to update the OS image while keeping the user files (by running the script against your existing installation but <u>leaving out</u> the --home-size-mb NNN option).

The ''livecd-iso-to-disk'' installation has the advantage over the ''LiveUSB-creator'' installation method by allowing a persistent /home/liveuser folder with the <tt>--home-size-mb ''NNN''</tt> option. This feature would allow you to update the OS image while keeping the user files (by running the script against your existing installation but <u>leaving out</u> the --home-size-mb NNN option).

* The <code>--unencrypted-home</code> option prevents password protection and encryption of the /home/liveuser folder. This releaves overhead on the compressed sqaushfs, and should be more robust to file system failures (outside of security).

* 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 (example, for 1 GB stick, use 200 for each).

@@ Line 7: / Line 7: @@
 == Linux instructions ==
-This is known to work in Fedora and Ubuntu 8.10 and should work in other Linux distributions.
+This is known to work in Fedora and Ubuntu and should work in other Linux distributions.
-* Make sure you have the ''isomd5sum'' and ''cryptsetup'' packages installed in your distribution, as they will be needed by the installation script.
+* Make sure you have the ''isomd5sum'', ''cryptsetup'', and ''syslinux'' packages installed in your distribution, as they will be needed by the "livecd-iso-to-disk" installation script. (On Ubuntu, <code>sudo apt-get install isomd5sum cryptsetup syslinux</code> will install the packages.)
-*:(These packages are needed for the verification and persistent home folder options of the installation script; they are not necessary if one applies the <tt>--noverify</tt> and <tt>--unencrypted-home</tt> options, respectively. The verification step checks that the file is complete after its travels, and it will signal a failure warning if there is a problem.)  The --unencrypted-home option may be preferred for improved robustness with the compressed file system employed by the LiveUSB deployment.
+**''isomd5sum'' is only needed for the recommended verification step, which checks that the .iso file is complete after its travels. The script will exit and provide a failure message if there is a problem with the file.  Verification can be bypassed by using the <tt>--noverify</tt> option.
+**''syslinux'' is needed to set up booting on the FAT file system of the USB disc or Live CD.
+**''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 <tt>--unencrypted-home</tt> 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.
 * Plug in a 1GB or larger USB stick into your computer.
 * Download the installation script: http://people.sugarlabs.org/sdz/livecd-iso-to-disk.sh (09 April 2009)
-:Ensure Ubuntu has the packages required to run the livecd-iso-to-disk.sh
-: <tt>sudo apt-get install isomd5sum cryptsetup syslinux</tt>
 * Check the USB device. In the example below the device is /dev/sdb:
 : <tt>df -h</tt>
@@ Line 62: / Line 63: @@
 * Run it as root, making sure to pass the correct USB device and to set overlay and home size appropriately, depending on the stick size.
 : <tt>sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-beta.iso /dev/sdb1</tt>
-The Linux installation has the advantage of allowing a persistent /home/liveuser folder with the <tt>--home-size-mb ''NNN''</tt> option. This feature would allow you to update the OS image while keeping the user files (by running the script against your existing installation but <u>leaving out</u> the --home-size-mb NNN option).
+The ''livecd-iso-to-disk'' installation has the advantage over the ''LiveUSB-creator'' installation method by allowing a persistent /home/liveuser folder with the <tt>--home-size-mb ''NNN''</tt> option. This feature would allow you to update the OS image while keeping the user files (by running the script against your existing installation but <u>leaving out</u> the --home-size-mb NNN option).
-* The <code>--unencrypted-home</code> option prevents password protection and encryption of the /home/liveuser folder. This releaves overhead on the compressed sqaushfs, and should be more robust to file system failures (outside of security).
 * 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 (example, for 1 GB stick, use 200 for each).