Sugar on a Stick/Linux - Revision history

FGrose at 16:10, 26 February 2015

2015-02-26T16:10:40Z

← Older revision		Revision as of 12:10, 26 February 2015
Line 4:		Line 4:
	== Introduction ==		== Introduction ==

	The page [[Sugar on a Stick/Linux/Installation]] provides ~~the~~ up to date and concise instructions for loading ~~'''[[Sugar on a Stick/10]]''',~~ the most recent, 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.		The page [[Sugar on a Stick/Linux/Installation]] provides up-to-date and concise instructions for loading the most recent released version of [[Sugar on a Stick]] (SoaS) onto a USB/SD flash storage device using GNU/Linux.

	==livecd-iso-to-disk tool==		==livecd-iso-to-disk tool==

FGrose: /* Load SoaS further insight */

2014-05-08T17:32:38Z

Load SoaS further insight

← Older revision		Revision as of 13:32, 8 May 2014
Line 135:		Line 135:
	:<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 '''800''' --unencrypted-home /run/initramfs/livedev /dev/sd'''?'''1</div>		:<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 '''800''' --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 ''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 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).
	::* A {{Code\|--delete-home}} option is available to avoid an error message while requesting both a new home (with {{Code\|--home-size-mb}}) when there is already a persistent home on the device). You wouldn't use the --delete-home option on an upgrade of the operating system only.		::* A {{Code\|--delete-home}} option is available to avoid an error message while requesting both a new home (with {{Code\|--home-size-mb}}) when there is already a persistent home on the device). You wouldn't use the --delete-home option on an upgrade of the operating 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 800 for the home folder).		: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 800 for the home folder).

Inkyfingers: /* Linux users, suggested methods */ clarify

2014-04-17T07:21:58Z

Linux users, suggested methods: clarify

← Older revision		Revision as of 03:21, 17 April 2014
Line 39:		Line 39:
	:: "1. Burn a CD-ROM disc, boot from it, then run the script, ''livecd-iso-to-disk''"		:: "1. Burn a CD-ROM disc, boot from it, then run the script, ''livecd-iso-to-disk''"

	: '''or''' create a Sugar image by dd or any of the methods on [[ Testing/Reports/Sugar_on_a_Stick_Persistence\|this page]]. Then boot into the Live OS, to create SoaS from the Live OS image.		: '''or''' create a Sugar image by dd or any of the methods on [[ Testing/Reports/Sugar_on_a_Stick_Persistence\|this page]]. Then boot into the Live OS, to create SoaS from the running Live OS image.

Inkyfingers: /* Introduction */ spelling

2014-04-17T07:18:26Z

Introduction: spelling

← Older revision		Revision as of 03:18, 17 April 2014
Line 4:		Line 4:
	== Introduction ==		== Introduction ==

	The page [[Sugar on a Stick/Linux/Installation]] provides the up to date and ~~consise~~ instructions for loading '''[[Sugar on a Stick/10]]''', the most recent, 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.		The page [[Sugar on a Stick/Linux/Installation]] provides the up to date and concise instructions for loading '''[[Sugar on a Stick/10]]''', the most recent, 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.

	==livecd-iso-to-disk tool==		==livecd-iso-to-disk tool==

Inkyfingers: Restructure page

2014-04-16T21:48:47Z

Restructure page

@@ Line 3: / Line 3: @@
 </noinclude>
 == Introduction ==
-: 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:
+The page [[Sugar on a Stick/Linux/Installation]] provides the up to date and consise instructions for loading '''[[Sugar on a Stick/10]]''', the most recent, 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.
 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!
-== Load SoaS onto a stick using Fedora or Ubuntu ==
+==Experimental==
-This is known to work in Fedora and Ubuntu.
+This is known to work in Fedora and has been reported to work in Ubuntu.
 First, download a SoaS {{Code|.iso}} image from  http://spins.fedoraproject.org/soas/#downloads, then return here.

FGrose: adjust sizes for SoaS 10

2013-12-14T17:40:41Z

adjust sizes for SoaS 10

Show changes

FGrose: --delete-home not needed with --format

2012-10-09T18:08:45Z

--delete-home not needed with --format

← Older revision		Revision as of 14:08, 9 October 2012
Line 88:		Line 88:
	:* repeat the steps for learning its device name (there can be situations when the device name has changed!)		:* repeat the steps for learning its device name (there can be situations when the device name has changed!)
	:* issue the command with the '''{{Code\|--format --msdos}}''' options, like this:		:* issue the command with the '''{{Code\|--format --msdos}}''' options, like this:
	{{Note/warning\|Warning\|The command described here will ~~not~~ ask for confirmation, and will '''destroy''' all pre-existing data on your USB device.<br>		{{Note/warning\|Warning\|The command described here will ask for a confirmation and will '''destroy''' all pre-existing data on your USB device.<br>
	See also [[olpc:How_to_Damage_a_FLASH_Storage_Device\|How to Damage a FLASH Storage Device]] for a discussion of why using the factory format is preferred.}}		See also [[olpc:How_to_Damage_a_FLASH_Storage_Device\|How to Damage a FLASH Storage Device]] for a discussion of why using the factory format is preferred.}}
	::<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 '''--format --msdos''' --overlay-size-mb '''500''' --home-size-mb '''900''' ~~--delete-home~~ --unencrypted-home '''/path/to/downloaded'''.iso /dev/sd'''?'''</div>		::<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 '''--format --msdos''' --overlay-size-mb '''500''' --home-size-mb '''900''' --unencrypted-home '''/path/to/downloaded'''.iso /dev/sd'''?'''</div>

	: {{Highlight\|In the above examples, 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\|In the above examples, the {{Code\|'''/path/to/downloaded'''.iso}} may be substituted with {{Code\|/dev/loop0}}, as this is the loop device that the mount command chose.}}

FGrose at 16:40, 9 October 2012

2012-10-09T16:40:45Z

← Older revision		Revision as of 12:40, 9 October 2012
Line 54:		Line 54:
	sudo fdisk -l		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		and looking in the output for the disk that corresponds to the USB device, e.g., a disk described with a stanza like

	Disk /dev/sd'''?''': 1939 MB, 1939865600 bytes		Disk /dev/sd'''?''': 1939 MB, 1939865600 bytes
Line 68:		Line 68:
	where '''?''' in /dev/sd'''?''' is (usually) a letter of the alphabet.		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.		If you have only '''one''' storage device with 2 GB of nominal capacity, it will be easy to recognize the USB device 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.		If you have '''more than one''' disk 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>		* Unmount the drive,<br>
Line 79:		Line 79:
	* 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.		* 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>		:<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:		: 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>		:<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'''?'''</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:		: If the command fails returning a complaint about the filesystem not being mounted, '''and''' you can afford to '''loose all data on the USB device''', you can try reformatting the USB device filesystem:

	:* mount the USB ~~key~~ (e.g. by unplugging and re-inserting it),		:* mount the USB device (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!!!)		:* repeat the steps for learning 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!!!~~''')		:* issue the command with the '''{{Code\|--format --msdos}}''' options, 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 '''--format''' --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-home /~~run~~/~~initramfs~~/~~livedev~~ /dev/sd'''???'''</div>		{{Note/warning\|Warning\|The command described here will not ask for confirmation, and will '''destroy''' all pre-existing data on your USB device.<br>
			See also [[olpc:How_to_Damage_a_FLASH_Storage_Device\|How to Damage a FLASH Storage Device]] for a discussion of why using the factory format is preferred.}}
			::<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 '''--format --msdos''' --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-home '''/path/to/downloaded'''.iso /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\|In the above examples, 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:}}		{{Note/note\|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>		:<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>

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

2012-10-09T13:47:44Z

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

← Older revision		Revision as of 09:47, 9 October 2012
Line 79:		Line 79:
	* 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.		* 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>		:<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.)		: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:}}		: {{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>		:<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 ''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.		::* 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.

Coltivare Fiori at 17:24, 7 October 2012

2012-10-07T17:24:27Z

@@ Line 49: / Line 49: @@
 /dev/sdc1     vfat    3.8G  4.0K  3.8G   1% /run/media/MyAccount/MyUSBdiscMountPoint
 </pre>
 * Unmount the drive,<br>