Sugar Labs - User contributions [en]

How to have spell-checking in Write Activity on Sugar 0.96.2

2012-10-31T20:17:13Z

Coltivare Fiori:

== What is spell-checking good for ==

Spell-checking can help children with writing disabilities/dyslexia improve their writing speed.

Since there is a minimum speed that children need to have to follow the meaning within the writing, spell-checking can make the difference between writing-without-understanding and writing-and-understanding.

== Spell-checking in the DEFAULT language of Sugar ==
To enable spell-checking in Write for the a document in a language that IS the DEFAULT language of Sugar, install (as suggested at http://forums.fedoraforum.org/archive/index.php/t-247039.html, and choosing Aspell as a spell-checker) the packages

# '''aspell''',
# '''aspell-<your language code>''', AND also
# '''enchant-aspell''', that is necessary for Abiword to use aspell.

In practice, do in a terminal (as root, or with '''sudo''', and being connected to the Internet)

# yum install aspell aspell-<the code of the default language on your Sugar> enchant-aspell

== Spell-checking in the rest of the languages ==

To enable spell-checking in Write for the a document in a language that IS NOT the DEFAULT language of Sugar, follow the instructions at
http://www.olpcnews.com/software/sugar/hacking_sugars_write_activity_to_support_spellchecking.html
and use the right-click (if your device allows it) to select the language of the document.

The language of the document can then be spell-checked if the spell-checker package corresponding to that language is installed.

In practice, do in a terminal (as root, or with '''sudo''', and being connected to the Internet)

# yum install aspell-<the code of the language of the document>

Then restart the Write Activity for that document, and spell-checking should start working in the non-default language.

== Getting help from the Spell-checker ==

When a word is marked as incorrect, right-click (if your device allows it) on the word marked as incorrect to get help.
If this does not work, follow - if you haven't already done so - the instructions at
http://www.olpcnews.com/software/sugar/hacking_sugars_write_activity_to_support_spellchecking.html
and try again.

How to have spellchecking in Write Activity on Sugar 0.96.2

2012-10-31T20:07:10Z

Coltivare Fiori: moved How to have spellchecking in Write Activity on Sugar 0.96.2 to How to have spell-checking in Write Activity on Sugar 0.96.2: The spell-checker warned me that "spellchecking" should be written "spell-checking" ;-)

#REDIRECT [[How to have spell-checking in Write Activity on Sugar 0.96.2]]

How to have spell-checking in Write Activity on Sugar 0.96.2

2012-10-31T20:07:10Z

= What is spell-checking good for =

Spell-checking can help children with writing disabilities/dyslexia improve their writing speed.

Since there is a minimum speed that children need to have to follow the meaning within the writing, spell-checking can make the difference between writing-without-understanding and writing-and-understanding.

= Spell-checking in the DEFAULT language of Sugar =
To enable spell-checking in Write for the a document in a language that IS the DEFAULT language of Sugar, install (as suggested at http://forums.fedoraforum.org/archive/index.php/t-247039.html, and choosing Aspell as a spell-checker) the packages

# '''aspell''',
# '''aspell-<your language code>''', AND also
# '''enchant-aspell''', that is necessary for Abiword to use aspell.

In practice, do in a terminal (as root, or with '''sudo''', and being connected to the Internet)

# yum install aspell aspell-<the code of the default language on your Sugar> enchant-aspell

= Spell-checking in the rest of the languages =

To enable spell-checking in Write for the a document in a language that IS NOT the DEFAULT language of Sugar, follow the instructions at
http://www.olpcnews.com/software/sugar/hacking_sugars_write_activity_to_support_spellchecking.html
and use the right-click (if your device allows it) to select the language of the document.

The language of the document can then be spell-checked if the spell-checker package corresponding to that language is installed.

In practice, do in a terminal (as root, or with '''sudo''', and being connected to the Internet)

# yum install aspell-<the code of the language of the document>

Then restart the Write Activity for that document, and spell-checking should start working in the non-default language.

= Getting help from the Spell-checker =

When a word is marked as incorrect, right-click (if your device allows it) on the word marked as incorrect to get help.
If this does not work, follow - if you haven't already done so - the instructions at
http://www.olpcnews.com/software/sugar/hacking_sugars_write_activity_to_support_spellchecking.html
and try again.

How to have spell-checking in Write Activity on Sugar 0.96.2

2012-10-31T20:04:44Z

Coltivare Fiori: /* What is spellchecking good for */

How to have spell-checking in Write Activity on Sugar 0.96.2

2012-10-31T20:04:19Z

Coltivare Fiori: Created page with "= What is spellchecking good for = Spellchecking can help children with writing disabilities/dyslexia improve their writing speed. Since there is a minimum speed that childr..."

= What is spellchecking good for =

Spellchecking can help children with writing disabilities/dyslexia improve their writing speed.

Since there is a minimum speed that children need to have to follow the meaning within the writing, spell-checking can make the difference between writing-without-understanding and writing-and-understanding.

= Spell-checking in the DEFAULT language of Sugar =
To enable spell-checking in Write for the a document in a language that IS the DEFAULT language of Sugar, install (as suggested at http://forums.fedoraforum.org/archive/index.php/t-247039.html, and choosing Aspell as a spell-checker) the packages

# '''aspell''',
# '''aspell-<your language code>''', AND also
# '''enchant-aspell''', that is necessary for Abiword to use aspell.

In practice, do in a terminal (as root, or with '''sudo''', and being connected to the Internet)

# yum install aspell aspell-<the code of the default language on your Sugar> enchant-aspell

= Spell-checking in the rest of the languages =

To enable spell-checking in Write for the a document in a language that IS NOT the DEFAULT language of Sugar, follow the instructions at
http://www.olpcnews.com/software/sugar/hacking_sugars_write_activity_to_support_spellchecking.html
and use the right-click (if your device allows it) to select the language of the document.

The language of the document can then be spell-checked if the spell-checker package corresponding to that language is installed.

In practice, do in a terminal (as root, or with '''sudo''', and being connected to the Internet)

# yum install aspell-<the code of the language of the document>

Then restart the Write Activity for that document, and spell-checking should start working in the non-default language.

= Getting help from the Spell-checker =

When a word is marked as incorrect, right-click (if your device allows it) on the word marked as incorrect to get help.
If this does not work, follow - if you haven't already done so - the instructions at
http://www.olpcnews.com/software/sugar/hacking_sugars_write_activity_to_support_spellchecking.html
and try again.

Sugar on a Stick/Linux

2012-10-09T13:47:44Z

Coltivare Fiori: Suggesting /run/initramfs/live/LiveOS/livecd-iso-to-disk [...] --format as discovered on an Ubuntu 12.04

<noinclude>
[[Category:HowTo]]
</noinclude>
== Introduction ==
This page provides additional detail for loading '''[[Sugar on a Stick/Quandong|Quandong]]''', the most stable, released version of Sugar on a Stick (SoaS), available at [[Sugar on a Stick/Downloads]], onto a USB/SD flash storage device using GNU/Linux.

: 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:

: [[Sugar on a Stick/Beta|SoaS 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]] | [[:Category:Live USB|Live USB: (all known portable Sugar distributions)]]

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!
* See this reference for more background details: [[fedora:How to create and use Live USB]]

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

This is known to work in Fedora and Ubuntu.

First, download a SoaS {{Code|.iso}} image from http://spins.fedoraproject.org/soas/#downloads, then return here.

* 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.)
:: <small>(On Gentoo, one needs to uncomment 'SAMPLE FILE' in /etc/mtools/mtools.conf to make syslinux work.)</small>
:*''[[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}} 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 2 GB or larger USB stick into your computer.
* Mount the 'SoaS.iso' image to reach the onboard livecd-iso-to-disk installation script:
: {{Code|sudo mkdir /media/soas/}}
: {{Code|sudo mount /path/to/Fedora-17-x86_64-Live-SoaS.iso /media/soas/}}
:: (mount: warning: /media/soas/ seems to be mounted read-only.)
* Change the working directory to the LiveOS folder on the SoaS.iso mount:
: {{Code|cd /media/soas/LiveOS}}
* Execute {{Code|./livecd-iso-to-disk --help}} for usage details. (The file is already executable.)

* Check the USB device node name on your system. In the example below, the <abbr title="small computer system interface">'''s'''csi</abbr> '''d'''evice is /dev/sdc and filesystem partition on that device is /dev/sdc1:
<pre>
$ df -Th
Filesystem Type Size Used Avail Use% Mounted on
rootfs rootfs 20G 12G 7.5G 61% /
udev devtmpfs 1.6G 0 1.6G 0% /dev
tmpfs tmpfs 1.6G 904K 1.6G 1% /dev/shm
tmpfs tmpfs 1.6G 788K 1.6G 1% /run
/dev/sda2 ext4 20G 12G 7.5G 61% /
tmpfs tmpfs 1.6G 0 1.6G 0% /sys/fs/cgroup
tmpfs tmpfs 1.6G 0 1.6G 0% /media
/dev/sda2 ext4 20G 12G 7.5G 61% /tmp
/dev/sda2 ext4 20G 12G 7.5G 61% /var/tmp
/dev/sda2 ext4 20G 12G 7.5G 61% /home
/dev/loop0 iso9660 509M 509M 0 100% /media/soas
/dev/sdc1 vfat 3.8G 4.0K 3.8G 1% /run/media/MyAccount/MyUSBdiscMountPoint
</pre>

Another way to find out the USB device node name on your system is issuing the command

sudo fdisk -l

and looking in the output for the disk that corresponds to the USB key, e.g. a disk described with a stanza like

Disk /dev/sd'''?''': 1939 MB, 1939865600 bytes
150 heads, 42 sectors/track, 601 cylinders, total 3788800 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e14bf

Device Boot Start End Blocks Id System
/dev/sd'''?'''1 * 2048 3784703 1891328 c W95 FAT32 (LBA)

where '''?''' in /dev/sd'''?''' is (usually) a letter of the alphabet.

If you have only '''one''' storage device with 2 Gb of nominal capacity, it will be easy to recognize the USB key in the fdisk output by looking at which device has (about) 2 Gb of capacity. In the example above, "Disk /dev/sd'''?'''" reports to be as large as ''1939 MB'', that is, almost 2 Gb.

Indeed, if you have '''more than one''' disks with about 2 Gb of capacity, consider moving to a situation where you'll have only '''one''' device with 2 Gb of capacity, because this will help out a lot in recognizing the drive correctly.

* Unmount the drive,<br>
: {{Code|sudo umount /run/media/MyAccount/MyUSBdiscMountPoint}}
:: <small>(The {{Code|/run/media/MyAccount/}} path is the new, Fedora 17 standard mount point. Other operating systems may use {{Code|/media/MyMountPoint}}.)</small>
{{:Sugar on a Stick/Linux/bootable device}}

* Run {{Code|livecd-iso-to-disk}} as the root user, making sure to pass the correct USB device node name and to set overlay and home size appropriately, depending on the target USB device storage capacity.
:<div style="padding: 1em; border: 1px dashed #2F6FAB; background-color: #FBFBFB; margin: 1em 0px 1em 0em; font-family: Courier;">./livecd-iso-to-disk --reset-mbr --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-home '''/path/to/downloaded'''.iso /dev/sd'''?'''1</div>
:If the command fails telling you that /dev/sd'''?'''1 does not exist, try using the command for /dev/sd'''?''' (the name of the device) and not for /dev/sd'''?'''1 (the name of the partition), like this:

:<div style="padding: 1em; border: 1px dashed #2F6FAB; background-color: #FBFBFB; margin: 1em 0px 1em 0em; font-family: Courier;">/run/initramfs/live/LiveOS/livecd-iso-to-disk --reset-mbr --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-home /run/initramfs/livedev /dev/sd'''?'''</div>

:If the command fails returning a complaint about the filesystem not mounted, '''and''' you can afford to '''loose all data on the USB key''', you can:

:* mount the USB key (e.g. by unplugging and re-inserting it),
:* repeat the steps for knowing its device name (there can be situations when the device name has changed!!!)
:* issue the command with the '''"--format option"''', like this ('''(WARNING!!!!!!!!!!!!! THE COMMAND DESCRIBED HERE WILL NOT ASK FOR CONFIRMATION AND WILL DESTROY ALL PRE-EXISTING DATA ON YOUR USB KEY!!!''')
::<div style="padding: 1em; border: 1px dashed #2F6FAB; background-color: #FBFBFB; margin: 1em 0px 1em 0em; font-family: Courier;">/run/initramfs/live/LiveOS/livecd-iso-to-disk --reset-mbr '''--format''' --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-home /run/initramfs/livedev /dev/sd'''???'''</div>

: {{Highlight|'''Note''':In the above example, the {{Code|'''/path/to/downloaded'''.iso}} may be substituted with {{Code|/dev/loop0}}, as this is the loop device that the mount command chose.}}

: {{Highlight|'''Note''': Additional USB or SD devices may be loaded from a running ''Sugar on a Stick'' image that was loaded with the livecd-iso-to-disk script (but not those installed by other methods) by running this command in the Terminal Activity as a root user:}}
:<div style="padding: 1em; border: 1px dashed #2F6FAB; background-color: #FBFBFB; margin: 1em 0px 1em 0em; font-family: Courier;">/run/initramfs/live/LiveOS/livecd-iso-to-disk --reset-mbr --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-home /run/initramfs/livedev /dev/sd'''?'''1</div>

: The ''livecd-iso-to-disk'' installation method has other advantages over the ''liveusb-creator'' method by allowing the creation of a separate, persistent /home/liveuser folder with the <tt>--home-size-mb ''NNN''</tt> option. This feature avoids consumption of the write-once persistent overlay for Activity storage (see [[LiveOS image]]) and allows one 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|--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}} and {{Code|--home-size-mb}} values (for example, for a 2 GB stick, use 500 for the overlay and 900 for the home folder).
:: If you have sufficient capacity on your target device, and format it with an ext[234] filesystem to overcome the 2048-MB fat32 file size limit, you may avoid the SquashFS compression by including the {{Code|--skipcompress}} option in the script command line.

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

===livecd-iso-to-disk transcript===

<pre>
[LiveOS]$ sudo ./livecd-iso-to-disk --reset-mbr --overlay-size-mb 500 --home-size-mb 900 --delete-home --unencrypted-home /media/SoaS/Fedora-17-x86_64-Live-SoaS.iso /dev/sdc1
Verifying image...
/media/SoaS/Fedora-17-x86_64-Live-SoaS.iso: 470134baa7e48085595243e53b55d41e
Fragment sums: 7de3e14f3d5aa991343fa35bdfe3a1db59d578db95a844a63d22de789de1
Fragment count: 20
Press [Esc] to abort check.
Checking: 100.0%

The media check is complete, the result is: PASS.

It is OK to use this media.
Copying live image to target device.
squashfs.img
512344064 100% 43.04MB/s 0:00:11 (xfer#1, to-check=0/1)

sent 512406681 bytes received 31 bytes 44557105.39 bytes/sec
total size is 512344064 speedup is 1.00
osmin.img
8192 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1)

sent 8265 bytes received 31 bytes 16592.00 bytes/sec
total size is 8192 speedup is 0.99
Updating boot config file
Initializing persistent overlay file
500+0 records in
500+0 records out
524288000 bytes (524 MB) copied, 5.1728 s, 101 MB/s
Initializing persistent /home
900+0 records in
900+0 records out
943718400 bytes (944 MB) copied, 152.195 s, 6.2 MB/s
Formatting unencrypted /home
mke2fs 1.42.3 (14-May-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
57600 inodes, 230400 blocks
11520 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=239075328
8 block groups
32768 blocks per group, 32768 fragments per group
7200 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

tune2fs 1.42.3 (14-May-2012)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
Installing boot loader
Target device is now set up with a Live image!
</pre>

== What's next? ==

After you've created your stick, it's time to [[Sugar on a Stick/Boot|boot your stick]] and [[Sugar on a Stick/Getting Involved | test]] it out. Please also [[Sugar on a Stick/Getting Involved/Testing | report]] your observations.

Sugar on a Stick/Linux

2012-10-07T17:24:27Z

Coltivare Fiori:

<noinclude>
[[Category:HowTo]]
</noinclude>
== Introduction ==
This page provides additional detail for loading '''[[Sugar on a Stick/Quandong|Quandong]]''', the most stable, released version of Sugar on a Stick (SoaS), available at [[Sugar on a Stick/Downloads]], onto a USB/SD flash storage device using GNU/Linux.

: 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:

: [[Sugar on a Stick/Beta|SoaS 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]] | [[:Category:Live USB|Live USB: (all known portable Sugar distributions)]]

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!
* See this reference for more background details: [[fedora:How to create and use Live USB]]

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

This is known to work in Fedora and Ubuntu.

First, download a SoaS {{Code|.iso}} image from http://spins.fedoraproject.org/soas/#downloads, then return here.

* 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.)
:: <small>(On Gentoo, one needs to uncomment 'SAMPLE FILE' in /etc/mtools/mtools.conf to make syslinux work.)</small>
:*''[[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}} 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 2 GB or larger USB stick into your computer.
* Mount the 'SoaS.iso' image to reach the onboard livecd-iso-to-disk installation script:
: {{Code|sudo mkdir /media/soas/}}
: {{Code|sudo mount /path/to/Fedora-17-x86_64-Live-SoaS.iso /media/soas/}}
:: (mount: warning: /media/soas/ seems to be mounted read-only.)
* Change the working directory to the LiveOS folder on the SoaS.iso mount:
: {{Code|cd /media/soas/LiveOS}}
* Execute {{Code|./livecd-iso-to-disk --help}} for usage details. (The file is already executable.)

* Check the USB device node name on your system. In the example below, the <abbr title="small computer system interface">'''s'''csi</abbr> '''d'''evice is /dev/sdc and filesystem partition on that device is /dev/sdc1:
<pre>
$ df -Th
Filesystem Type Size Used Avail Use% Mounted on
rootfs rootfs 20G 12G 7.5G 61% /
udev devtmpfs 1.6G 0 1.6G 0% /dev
tmpfs tmpfs 1.6G 904K 1.6G 1% /dev/shm
tmpfs tmpfs 1.6G 788K 1.6G 1% /run
/dev/sda2 ext4 20G 12G 7.5G 61% /
tmpfs tmpfs 1.6G 0 1.6G 0% /sys/fs/cgroup
tmpfs tmpfs 1.6G 0 1.6G 0% /media
/dev/sda2 ext4 20G 12G 7.5G 61% /tmp
/dev/sda2 ext4 20G 12G 7.5G 61% /var/tmp
/dev/sda2 ext4 20G 12G 7.5G 61% /home
/dev/loop0 iso9660 509M 509M 0 100% /media/soas
/dev/sdc1 vfat 3.8G 4.0K 3.8G 1% /run/media/MyAccount/MyUSBdiscMountPoint
</pre>

Another way to find out the USB device node name on your system is issuing the command

sudo fdisk -l

and looking in the output for the disk that corresponds to the USB key, e.g. a disk described with a stanza like

Disk /dev/sd'''?''': 1939 MB, 1939865600 bytes
150 heads, 42 sectors/track, 601 cylinders, total 3788800 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e14bf

Device Boot Start End Blocks Id System
/dev/sd'''?'''1 * 2048 3784703 1891328 c W95 FAT32 (LBA)

where '''?''' in /dev/sd'''?''' is (usually) a letter of the alphabet.

If you have only '''one''' storage device with 2 Gb of nominal capacity, it will be easy to recognize the USB key in the fdisk output by looking at which device has (about) 2 Gb of capacity. In the example above, "Disk /dev/sd'''?'''" reports to be as large as ''1939 MB'', that is, almost 2 Gb.

Indeed, if you have '''more than one''' disks with about 2 Gb of capacity, consider moving to a situation where you'll have only '''one''' device with 2 Gb of capacity, because this will help out a lot in recognizing the drive correctly.

* Unmount the drive,<br>
: {{Code|sudo umount /run/media/MyAccount/MyUSBdiscMountPoint}}
:: <small>(The {{Code|/run/media/MyAccount/}} path is the new, Fedora 17 standard mount point. Other operating systems may use {{Code|/media/MyMountPoint}}.)</small>
{{:Sugar on a Stick/Linux/bootable device}}

* Run {{Code|livecd-iso-to-disk}} as the root user, making sure to pass the correct USB device node name and to set overlay and home size appropriately, depending on the target USB device storage capacity.
:<div style="padding: 1em; border: 1px dashed #2F6FAB; background-color: #FBFBFB; margin: 1em 0px 1em 0em; font-family: Courier;">./livecd-iso-to-disk --reset-mbr --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-home '''/path/to/downloaded'''.iso /dev/sd'''?'''1</div>
:: (In the above example, the {{Code|'''/path/to/downloaded'''.iso}} may be substituted with {{Code|/dev/loop0}}, as this is the loop device that the mount command chose.)
: {{Highlight|'''Note''': Additional USB or SD devices may be loaded from a running ''Sugar on a Stick'' image that was loaded with the livecd-iso-to-disk script (but not those installed by other methods) by running this command in the Terminal Activity as a root user:}}
:<div style="padding: 1em; border: 1px dashed #2F6FAB; background-color: #FBFBFB; margin: 1em 0px 1em 0em; font-family: Courier;">/run/initramfs/live/LiveOS/livecd-iso-to-disk --reset-mbr --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-home /run/initramfs/livedev /dev/sd'''?'''1</div>
: The ''livecd-iso-to-disk'' installation method has other advantages over the ''liveusb-creator'' method by allowing the creation of a separate, persistent /home/liveuser folder with the <tt>--home-size-mb ''NNN''</tt> option. This feature avoids consumption of the write-once persistent overlay for Activity storage (see [[LiveOS image]]) and allows one 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|--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}} and {{Code|--home-size-mb}} values (for example, for a 2 GB stick, use 500 for the overlay and 900 for the home folder).
:: If you have sufficient capacity on your target device, and format it with an ext[234] filesystem to overcome the 2048-MB fat32 file size limit, you may avoid the SquashFS compression by including the {{Code|--skipcompress}} option in the script command line.

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

===livecd-iso-to-disk transcript===

<pre>
[LiveOS]$ sudo ./livecd-iso-to-disk --reset-mbr --overlay-size-mb 500 --home-size-mb 900 --delete-home --unencrypted-home /media/SoaS/Fedora-17-x86_64-Live-SoaS.iso /dev/sdc1
Verifying image...
/media/SoaS/Fedora-17-x86_64-Live-SoaS.iso: 470134baa7e48085595243e53b55d41e
Fragment sums: 7de3e14f3d5aa991343fa35bdfe3a1db59d578db95a844a63d22de789de1
Fragment count: 20
Press [Esc] to abort check.
Checking: 100.0%

The media check is complete, the result is: PASS.

It is OK to use this media.
Copying live image to target device.
squashfs.img
512344064 100% 43.04MB/s 0:00:11 (xfer#1, to-check=0/1)

sent 512406681 bytes received 31 bytes 44557105.39 bytes/sec
total size is 512344064 speedup is 1.00
osmin.img
8192 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1)

sent 8265 bytes received 31 bytes 16592.00 bytes/sec
total size is 8192 speedup is 0.99
Updating boot config file
Initializing persistent overlay file
500+0 records in
500+0 records out
524288000 bytes (524 MB) copied, 5.1728 s, 101 MB/s
Initializing persistent /home
900+0 records in
900+0 records out
943718400 bytes (944 MB) copied, 152.195 s, 6.2 MB/s
Formatting unencrypted /home
mke2fs 1.42.3 (14-May-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
57600 inodes, 230400 blocks
11520 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=239075328
8 block groups
32768 blocks per group, 32768 fragments per group
7200 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

tune2fs 1.42.3 (14-May-2012)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
Installing boot loader
Target device is now set up with a Live image!
</pre>

== What's next? ==

After you've created your stick, it's time to [[Sugar on a Stick/Boot|boot your stick]] and [[Sugar on a Stick/Getting Involved | test]] it out. Please also [[Sugar on a Stick/Getting Involved/Testing | report]] your observations.