Changes

Sugar on a Stick/Linux (view source)

Revision as of 14:42, 6 May 2010

219 bytes added , 14:42, 6 May 2010

no edit summary

Line 5: Line 5:

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

−

+

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!

Line 14: Line 14:

This is known to work in Fedora and Ubuntu.

−

First, download a SoaS-2-blueberry ~~<tt>~~.iso~~</tt>~~ image from [[http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso], then return here.

+

First, download a SoaS-2-blueberry {{Code|.iso}} image from [[http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso], 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:)

Line 20: Line 20:

removed above, see warning at http://fedoraproject.org/wiki/How_to_create_and_use_Live_USB

-->

−

* 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}} 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.)

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

:*''[[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.

−

:*''[[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.

+

:*''[[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}} option. The {{Code|--unencrypted-home}} 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 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). (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). (See [[fedora:Livecd-iso-to-disk.pod]] for usage details.) (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:

: <tt>'''df -h'''</tt>

Line 40: Line 40:

* Unmount the drive,

−

: ~~<tt>~~sudo umount /dev/sd''b1''~~</tt>~~

+

: {{Code|sudo umount /dev/sd''b1''}}

* Then check to see that the partition is marked as bootable,

−

: ~~<tt>~~sudo fdisk '''-l'''~~</tt>~~ ''<----that's a lowercase letter 'L' for the '''l'''ist option.''

+

: {{Code|sudo fdisk '''-l'''}} ''<----that's a lowercase letter 'L' for the '''l'''ist option.''

You should see output that looks like this:

Disk /dev/sdb: 1047 MB, 1047265280 bytes

Line 62: Line 62:

:* For Fedora,

−

::# ~~<tt>~~parted /dev/sd''b''~~</tt>~~

+

::# {{Code|parted /dev/sd''b''}}

−

::# toggle 1 boot

+

::# {{Code|toggle 1 boot}}

−

::# quit

+

::# {{Code|quit}}

* Change mode to make the script executable.

−

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

+

: {{Code|chmod +x livecd-iso-to-disk.sh}}

* 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-strawberry.iso /dev/sd''b1''~~</tt>~~

+

: {{Code|sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-strawberry.iso /dev/sd''b1''}}

:: '''Note:''' With the soas-2-blueberry.iso, leave out the 3 options for a separate persistent home. The script will complete successfully, but the new installation startup process will have trouble finding the home folder and fail to complete.

:: Normally, 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 leaving out the --home-size-mb NNN option).

−

::* 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}} option is used to avoid an error message while requesting both a new home (with {{Code|--home-size-mb}}) and a persistent home (indirectly with {{Code|--unencrypted-home}}). 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}} and {{Code|--home-size-mb}} 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.

+

:: If you have sufficient capacity on your target device, you may avoid the file system compression by including the {{Code|--skipcompress}} option to the script command.

+

<!--:* 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>~~

+

:::{{Code|#!/bin/bash}}

−

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

+

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

:* Watch out for errors in the output of the script, the script seems to ignore them! (and say all is fine on the last line).

FGrose

Bureaucrats, Check users, Administrators, Widget editors

8,288

edits