SoaS Blueberry Instructions - Revision history

FGrose: update Macintosh link

2012-07-01T00:50:47Z

update Macintosh link

← Older revision		Revision as of 20:50, 30 June 2012
Line 86:		Line 86:
	''Sugar on a Stick Blueberry and Strawberry images are for the Intel processor.''<br>		''Sugar on a Stick Blueberry and Strawberry images are for the Intel processor.''<br>
	''See [[#Older Mac with powerPC processor \| Using Sugar with powerPC]] if you do not have an Intel processor.''		''See [[#Older Mac with powerPC processor \| Using Sugar with powerPC]] if you do not have an Intel processor.''
	* See also [[~~Sugar on a Stick/Mac~~]].		* See also [[Macintosh]].

	====To identify the Mac's processor and OS X version====		====To identify the Mac's processor and OS X version====

FGrose: remove broken link

2011-10-23T17:32:39Z

remove broken link

← Older revision		Revision as of 13:32, 23 October 2011
Line 12:		Line 12:
	\|valign=top\|		\|valign=top\|
	# Download the latest version of the '''Fedora LiveUSB Creator''' from [https://fedorahosted.org/liveusb-creator/#Download FedoraHosted here].		# Download the latest version of the '''Fedora LiveUSB Creator''' from [https://fedorahosted.org/liveusb-creator/#Download FedoraHosted here].
	# Plug a blank target USB flash drive (or SD Card) into your computer (1GB or greater). ~~(See [[Category:Live_USB#Cautions_with_using_Live_USB.27s \|Cautions with using Live USB]] regarding flash drive size.)~~		# Plug a blank target USB flash drive (or SD Card) into your computer (1GB or greater).
	# Launch LiveUSB Creator.		# Launch LiveUSB Creator.
	# Select '''Sugar on a Stick v2 Blueberry''' in the drop-down menu on the upper-right side to download the liveUSB disk image.		# Select '''Sugar on a Stick v2 Blueberry''' in the drop-down menu on the upper-right side to download the liveUSB disk image.

FGrose at 17:28, 28 August 2011

2011-08-28T17:28:24Z

← Older revision		Revision as of 13:28, 28 August 2011
Line 12:		Line 12:
	\|valign=top\|		\|valign=top\|
	# Download the latest version of the '''Fedora LiveUSB Creator''' from [https://fedorahosted.org/liveusb-creator/#Download FedoraHosted here].		# Download the latest version of the '''Fedora LiveUSB Creator''' from [https://fedorahosted.org/liveusb-creator/#Download FedoraHosted here].
	# Plug a blank target USB flash drive (or SD Card) into your computer (1GB or greater). (See [~~http://wiki.sugarlabs.org/go/~~Category:Live_USB#Cautions_with_using_Live_USB.27s Cautions with using Live USB] regarding flash drive size.)		# Plug a blank target USB flash drive (or SD Card) into your computer (1GB or greater). (See [[Category:Live_USB#Cautions_with_using_Live_USB.27s \|Cautions with using Live USB]] regarding flash drive size.)
	# Launch LiveUSB Creator.		# Launch LiveUSB Creator.
	# Select '''Sugar on a Stick v2 Blueberry''' in the drop-down menu on the upper-right side to download the liveUSB disk image.		# Select '''Sugar on a Stick v2 Blueberry''' in the drop-down menu on the upper-right side to download the liveUSB disk image.
Line 26:		Line 26:

	::# In Windows, download the latest version of the [http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso Live CD image], and burn the image to a CD.		::# In Windows, download the latest version of the [http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso Live CD image], and burn the image to a CD.
	::# Follow the instructions [~~http://wiki.sugarlabs.org/go/~~Sugar_on_a_Stick/ZyX-LiveInstaller here] to create the bootable Sugar/Blueberry USB flash drive by (i) booting the PC into Sugar with the CD and (ii) running ZyX-LiveInstaller within the Terminal activity. You will also need a spare, blank (or erasable) USB flash drive -- preferably manufactured by a different manufacturer than the target USB -- to use as a swap drive during the procedure. Any data on the swap drive will be wiped.		::# Follow the instructions [[Sugar_on_a_Stick/ZyX-LiveInstaller \|here]] to create the bootable Sugar/Blueberry USB flash drive by (i) booting the PC into Sugar with the CD and (ii) running ZyX-LiveInstaller within the Terminal activity. You will also need a spare, blank (or erasable) USB flash drive -- preferably manufactured by a different manufacturer than the target USB -- to use as a swap drive during the procedure. Any data on the swap drive will be wiped.

	Notes:		Notes:
Line 36:		Line 36:
	* Option #2 creates a more-robust, more-stable drive whose free space can be monitored using the Terminal activity. Non-compressed SoaS drives, however, are not bootable with a boot helper CD.		* Option #2 creates a more-robust, more-stable drive whose free space can be monitored using the Terminal activity. Non-compressed SoaS drives, however, are not bootable with a boot helper CD.

	== For GNU/Linux ~~Users~~ ==		== For GNU/Linux users ==

	1-)Linux Users will use a slightly different approach than Windows ~~Users~~ to ensure maximum compatibility		1. Linux Users will use a slightly different approach than Windows users to ensure maximum compatibility
	with different distributions. Please follow the instructions carefully to ensure your data is preserved.		with different distributions. Please follow the instructions carefully to ensure your data is preserved.

Line 52:		Line 52:
	* Launch LiveUSB Creator and follow the instructions [[SoaS_Blueberry_Instructions#For_Windows_Users\|above]].		* Launch LiveUSB Creator and follow the instructions [[SoaS_Blueberry_Instructions#For_Windows_Users\|above]].

	2-)If you use any '''other distribution''', download the '''image-writer''' tool from [http://download.sugarlabs.org/soas/releases/image-writer here] and the '''live image''' from [http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso here].		2. If you use any '''other distribution''', download the '''image-writer''' tool from [http://download.sugarlabs.org/soas/releases/image-writer here] and the '''live image''' from [http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso here].

	'''This solution will not create a persistent storage overlay'''		'''This solution will not create a persistent storage overlay'''
Line 62:		Line 62:
	* You will be notified once the process has finished.		* You will be notified once the process has finished.

	3-)'''zyx-liveinstaller:'''[~~http://wiki.sugarlabs.org/go/Sugar_on_a_Stick~~/ZyX-LiveInstaller]		3. '''zyx-liveinstaller:''' [[Sugar on a Stick/ZyX-LiveInstaller]]

	4~~-)Unsupported~~''' ~~instructions~~ for ~~creating a key~~ with persistent storage for Blueberry:''' [~~http://wiki.sugarlabs.org/go/~~Talk:~~SoaS_Blueberry_Instructions~~] ~~and~~ on ~~other distributions are available here:[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick~~/Linux]		4. '''Instructions for installing with persistent storage for Blueberry: ''' [[Talk:SoaS Blueberry Instructions]]. See also [[Sugar on a Stick/Linux]].

	== Boot Helper ==		== Boot Helper ==
Line 79:		Line 79:

	<!--		<!--
	template does not allow enough separation between disparate sections. Try using wiki sections with the ===section_title=== wikiformat. See ~~http://wiki.sugarlabs.org/go/Wiki_Team~~/Guide/Formatting. If that is not sufficient, a skin change would be required to avoid the newline and <br> workarounds. Please post a screenshot of your issue. We are planning skin changes (see [[Wiki_Team/Roadmap/Wiki_skin_redesign]]). Comments are usually left on the Discussion/Talk pages for greater visibility and ease of linking. Changes to either page trigger watchlist notifications. Thanks again for your edits!		template does not allow enough separation between disparate sections. Try using wiki sections with the ===section_title=== wikiformat. See [[Wiki Team/Guide/Formatting]]. If that is not sufficient, a skin change would be required to avoid the newline and <br> workarounds. Please post a screenshot of your issue. We are planning skin changes (see [[Wiki_Team/Roadmap/Wiki_skin_redesign]]). Comments are usually left on the Discussion/Talk pages for greater visibility and ease of linking. Changes to either page trigger watchlist notifications. Thanks again for your edits!
	-->		-->
	== For Mac OS X Users ==		== For Mac OS X Users ==
	~~<div style="background: #ffe792; padding: 10px; border: 1px solid #cde7a8" align=left>'''~~NOTE to Instruction Editors:~~'''~~ Please test and adjust instructions for the soon-to-be-released [[Sugar on a Stick/Mirabelle]].		{{Note/help\|NOTE to Instruction Editors:\|Please test and adjust instructions for the soon-to-be-released [[Sugar on a Stick/Mirabelle]]. Draft instructions at [[Sugar on a Stick/Beta]].}}
	Draft instructions at [[Sugar on a Stick/Beta~~]] and [[SoaS Mirabelle Instructions~~]].~~</div>~~

	''Sugar on a Stick Blueberry and Strawberry images are for the Intel processor.''<br>		''Sugar on a Stick Blueberry and Strawberry images are for the Intel processor.''<br>
Line 139:		Line 138:
	**you may release the c key once the sugar logo appears.		**you may release the c key once the sugar logo appears.

	===Suggestion: Using ~~boot_helper_disk_with_blueberry_usb_on_intel_mac (~~may fix bugs listed below~~)===~~		===Suggestion: ===
	~~'''Link:'''~~[~~http://wiki.sugarlabs.org/go/~~Talk:~~SoaS_Blueberry_Instructions~~#~~Using_boot_helper_disk_with_blueberry_usb_on_intel_mac~~]		Using a boot helper disc may fix the bugs listed below. See [[Talk:SoaS Blueberry Instructions#Using boot helper disk with blueberry usb on intel mac\|these instructions]].


	==== Mac Bugs ====		==== Mac Bugs ====

Interested: /* To calculate a file's SHA-1 checksum */

2010-05-12T03:34:53Z

To calculate a file's SHA-1 checksum

← Older revision		Revision as of 23:34, 11 May 2010
Line 106:		Line 106:

	'''To install Sugar onto a Stick'''		'''To install Sugar onto a Stick'''
	* Download the [http://download.sugarlabs.org/soas/releases/image-writer-mac image-writer for Mac ~~computers~~ ]<br>~~(If you get an error from~~ PythonLauncher~~, it~~ may ~~be because you are trying to~~ open the file, don't do that, just download it).~~<br>~~Verify the file was downloaded properly ''by calculating its [http://download.sugarlabs.org/soas/releases/SHA1SUM SHA-1 checksum]''<br>For protection against tampering and transmission errors, '''always compare the checksum of each download'''.		* Download the [http://download.sugarlabs.org/soas/releases/image-writer-mac image-writer for Mac ]<br>''PythonLauncher may automatically open the file; don't allow that, just download it.''

			* Verify the file was downloaded properly ''by calculating its [http://download.sugarlabs.org/soas/releases/SHA1SUM SHA-1 checksum]''<br>For protection against tampering and transmission errors, '''always compare the checksum of each download'''.

	* Eject all USB drives. Insert the flash drive you wish to install Sugar on a Stick.<br>'''WARNING:''' your entire flash drive will be overwritten in the next step! All partitions will be erased.		* Eject all USB drives. Insert the flash drive you wish to install Sugar on a Stick.<br>'''WARNING:''' your entire flash drive will be overwritten in the next step! All partitions will be erased.
Line 122:		Line 124:

	'''To create a Boot Helper CD'''<br>		'''To create a Boot Helper CD'''<br>
	* Download the USB boot helper [http://download.sugarlabs.org/soas/releases/soas-2-boot.iso soas-2-boot.iso]~~<br>~~Verify the file was downloaded properly ''by calculating its [http://download.sugarlabs.org/soas/releases/SHA1SUM SHA-1 checksum]''<br>For protection against tampering and transmission errors, '''always compare the checksum of each download'''.		* Download the USB boot helper [http://download.sugarlabs.org/soas/releases/soas-2-boot.iso soas-2-boot.iso]
	* Open the ~~disk~~ Utility. Drag the downloaded soas-2-boot.iso to the bottom of the list.		* Verify the file was downloaded properly ''by calculating its [http://download.sugarlabs.org/soas/releases/SHA1SUM SHA-1 checksum]''<br>For protection against tampering and transmission errors, '''always compare the checksum of each download'''.
			* Open the Disk Utility. Drag the downloaded soas-2-boot.iso to the bottom of the list.
	* Select the Disc Image in the list, then press the Burn button.		* Select the Disc Image in the list, then press the Burn button.
	* Insert a blank disc when prompted.		* Insert a blank disc when prompted.

FGrose at 03:19, 12 May 2010

2010-05-12T03:19:04Z

← Older revision		Revision as of 23:19, 11 May 2010
Line 82:		Line 82:
	-->		-->
	== For Mac OS X Users ==		== For Mac OS X Users ==
			<div style="background: #ffe792; padding: 10px; border: 1px solid #cde7a8" align=left>'''NOTE to Instruction Editors:''' Please test and adjust instructions for the soon-to-be-released [[Sugar on a Stick/Mirabelle]].
			Draft instructions at [[Sugar on a Stick/Beta]] and [[SoaS Mirabelle Instructions]].</div>

	''Sugar on a Stick Blueberry and Strawberry images are for the Intel processor.''<br>		''Sugar on a Stick Blueberry and Strawberry images are for the Intel processor.''<br>
	''See [[#Older Mac with powerPC processor \| Using Sugar with powerPC]] if you do not have an Intel processor.''		''See [[#Older Mac with powerPC processor \| Using Sugar with powerPC]] if you do not have an Intel processor.''
Line 148:		Line 151:
	** append selinux=0 to the kernel's list of boot parameters.		** append selinux=0 to the kernel's list of boot parameters.
	** press return or enter to continue the boot process.		** press return or enter to continue the boot process.
	Submit bugs to request a different flavor of boot helper CD that boots Mac automatically, without typing selinux=0~~<!--~~ and removes the countdown, Macs innately have the option key interrupt, the mouse down interrupt and the power button interrupt to handle this boot time issue.~~-->~~		Submit bugs to request a different flavor of boot helper CD that boots Mac automatically, without typing selinux=0 and removes the countdown, Macs innately have the option key interrupt, the mouse down interrupt and the power button interrupt to handle this boot time issue.
	<br>		<br>
	*BootHelperCD will not boot sticks created by a Mac:		*BootHelperCD will not boot sticks created by a Mac:

Interested: /* Suggestion: Using boot_helper_disk_with_blueberry_usb_on_intel_mac (may fix bugs listed below) */

2010-05-12T02:45:26Z

Suggestion: Using boot_helper_disk_with_blueberry_usb_on_intel_mac (may fix bugs listed below)

Interested at 02:14, 12 May 2010

2010-05-12T02:14:24Z

← Older revision		Revision as of 22:14, 11 May 2010
Line 138:		Line 138:
	''The boot sequence does not work properly due to minor bugs. Follow these workarounds to boot an intel Mac.''<br>''Note: to the child it is named SUGAR. But the stick they take home is named FEDORA.''<!-- How do you file style bugs?		''The boot sequence does not work properly due to minor bugs. Follow these workarounds to boot an intel Mac.''<br>''Note: to the child it is named SUGAR. But the stick they take home is named FEDORA.''<!-- How do you file style bugs?
	bugs.sugarlabs.org will take task and enhancement requests in addition to defect reports.		bugs.sugarlabs.org will take task and enhancement requests in addition to defect reports.
	Forcing users to rename their USB sticks something esoteric like FEDORA is just wrong~~, it should default to SUGAR. While I'm whining, I'd prefer something more legible than white text on white background when entering secret codes.~~		Forcing users to rename their USB sticks something esoteric like FEDORA is just wrong -->

	See the end of this discussion, http://answers.edge.launchpad.net/soas/+question/95622. It provides a way to edit the boot kernel arguments to boot on a Mac. You may be able to advance the instructions from there.

	-->		<!--I'd prefer something more legible than white text on white background when entering secret codes. -->
			*BootHelperCD cannot boot Mac without typing secret code into difficult to read window:<br> ''See [[#Boot Helper \| Boot Helper ]]... "If your boot hangs..." for complete details''
	*~~image~~-~~writer~~-~~mac~~ and BootHelperCD ~~are~~ not ~~compatible:~~		<!--See the end of this discussion, http://answers.edge.launchpad.net/soas/+question/95622. It provides a way to edit the boot kernel arguments to boot on a Mac. You may be able to advance the instructions from there. -->
			** interrupt the boot sequence
			** append selinux=0 to the kernel's list of boot parameters.
			** press return or enter to continue the boot process.
			Submit bugs to request a different flavor of boot helper CD that boots Mac automatically, without typing selinux=0<!-- and removes the countdown, Macs innately have the option key interrupt, the mouse down interrupt and the power button interrupt to handle this boot time issue.-->
			<br>
			*BootHelperCD will not boot sticks created by a Mac.
	** BootHelperCD can only boot sticks named FEDORA.		** BootHelperCD can only boot sticks named FEDORA.
	** Image-writer ~~gives the USB stick~~ the name of blueberry-2-soas.		** Image-writer-mac writes the name blueberry-2-soas onto the stick.
	** USB stick is created as read only. So the name is not easily changed by mere mortals.		** USB stick is created as read only. So the name is not easily changed by mere mortals.
	This is a showstopper.<br>You cannot boot without hacking the USB stick name.<br>Use a windows ~~machine~~ to create Sugar on a Stick, named FEDORA, with persistent overlay.		This is a showstopper.<br>You cannot boot without hacking the USB stick name.<br>Use windows instructions to create Sugar on a Stick, named FEDORA, with persistent overlay.
			<br>
	*Sugar on a Stick is READ-ONLY		*Sugar on a Stick is READ-ONLY
	**Nothing is saved between reboots. Sugar asks for your name and colors each boot.		**Nothing is saved between reboots. Sugar asks for your name and colors each boot.
	**image-writer-mac does not create a persistent overlay file.		**image-writer-mac does not create a persistent overlay file.
	There is no way to create a persistent overlay on Mac without hacking the USB stick.<br>Use a windows ~~machine~~ to create Sugar on a Stick, named FEDORA, with persistent overlay.		There is no way to create a persistent overlay on Mac without hacking the USB stick.<br>Use windows instructions to create Sugar on a Stick, named FEDORA, with persistent overlay.

	*BootHelperCD cannot boot Mac without typing secret code into difficult to read window:<br> ''See [[#Boot Helper \| Boot Helper ]]... "If your boot hangs..." for complete details''
	** interrupt the boot sequence
	** append selinux=0 to the kernel's list of boot parameters.
	** press return or enter to continue the boot process.
	Submit bugs to request a different flavor of boot helper CD that boots Mac automatically, without typing selinux=0<!-- and removes the countdown, Macs innately have the option key interrupt, the mouse down interrupt and the power button interrupt to handle this boot time issue.-->

	====Older Mac with powerPC processor====		====Older Mac with powerPC processor====

FGrose: /* For Mac OS X Users */

2010-04-13T16:04:57Z

For Mac OS X Users

← Older revision		Revision as of 12:04, 13 April 2010
Line 84:		Line 84:
	''Sugar on a Stick Blueberry and Strawberry images are for the Intel processor.''<br>		''Sugar on a Stick Blueberry and Strawberry images are for the Intel processor.''<br>
	''See [[#Older Mac with powerPC processor \| Using Sugar with powerPC]] if you do not have an Intel processor.''		''See [[#Older Mac with powerPC processor \| Using Sugar with powerPC]] if you do not have an Intel processor.''
			* See also [[Sugar on a Stick/Mac]].

	====To identify the Mac's processor and OS X version====		====To identify the Mac's processor and OS X version====

Satellit: /* Suggestion: Using boot_helper_disk_with_blueberry_usb_on_intel_mac */

2010-04-08T12:36:26Z

Suggestion: Using boot_helper_disk_with_blueberry_usb_on_intel_mac

← Older revision		Revision as of 08:36, 8 April 2010
Line 132:		Line 132:
	**you may release the c key once the sugar logo appears.		**you may release the c key once the sugar logo appears.

	===Suggestion: Using boot_helper_disk_with_blueberry_usb_on_intel_mac===		===Suggestion: Using boot_helper_disk_with_blueberry_usb_on_intel_mac (may fix bugs listed below)===
	'''Link:'''[http://wiki.sugarlabs.org/go/Talk:SoaS_Blueberry_Instructions#Using_boot_helper_disk_with_blueberry_usb_on_intel_mac]		'''Link:'''[http://wiki.sugarlabs.org/go/Talk:SoaS_Blueberry_Instructions#Using_boot_helper_disk_with_blueberry_usb_on_intel_mac]
	==== Mac Boot Bugs ====		==== Mac Boot Bugs ====

Quozl: /* To calculate a file's SHA-1 checksum */

2010-04-08T06:12:45Z

To calculate a file's SHA-1 checksum

← Older revision		Revision as of 02:12, 8 April 2010
Line 102:		Line 102:

	'''To install Sugar onto a Stick'''		'''To install Sugar onto a Stick'''
	* Download the [http://download.sugarlabs.org/soas/releases/image-writer-mac image-writer for Mac computers ]<br>If you get an error from PythonLauncher, ~~retry~~ the download ~~with Alt-Click or Option-Click~~.<br>Verify the file was downloaded properly ''by calculating its [http://download.sugarlabs.org/soas/releases/SHA1SUM SHA-1 checksum]''<br>For protection against tampering and transmission errors, '''always compare the checksum of each download'''.		* Download the [http://download.sugarlabs.org/soas/releases/image-writer-mac image-writer for Mac computers ]<br>(If you get an error from PythonLauncher, it may be because you are trying to open the file, don't do that, just download it).<br>Verify the file was downloaded properly ''by calculating its [http://download.sugarlabs.org/soas/releases/SHA1SUM SHA-1 checksum]''<br>For protection against tampering and transmission errors, '''always compare the checksum of each download'''.

	* Eject all USB drives. Insert the flash drive you wish to install Sugar on a Stick.<br>'''WARNING:''' your entire flash drive will be overwritten in the next step! All partitions will be erased.		* Eject all USB drives. Insert the flash drive you wish to install Sugar on a Stick.<br>'''WARNING:''' your entire flash drive will be overwritten in the next step! All partitions will be erased.

← Older revision		Revision as of 22:45, 11 May 2010
Line 135:		Line 135:
	===Suggestion: Using boot_helper_disk_with_blueberry_usb_on_intel_mac (may fix bugs listed below)===		===Suggestion: Using boot_helper_disk_with_blueberry_usb_on_intel_mac (may fix bugs listed below)===
	'''Link:'''[http://wiki.sugarlabs.org/go/Talk:SoaS_Blueberry_Instructions#Using_boot_helper_disk_with_blueberry_usb_on_intel_mac]		'''Link:'''[http://wiki.sugarlabs.org/go/Talk:SoaS_Blueberry_Instructions#Using_boot_helper_disk_with_blueberry_usb_on_intel_mac]
	==== Mac ~~Boot~~ Bugs ====
	''The boot sequence does not work properly due to minor bugs. Follow these workarounds to boot an intel Mac.''<br>''Note: to the child it is named SUGAR. But the stick they take home is named FEDORA.''<!-- How do you file style bugs?
			==== Mac Bugs ====
			''The boot sequence does not work properly due to minor bugs. Follow these workarounds to boot an intel Mac''<br>''Note: to the child it is named SUGAR. But the stick they take home is named FEDORA.''<!-- How do you file style bugs?
	bugs.sugarlabs.org will take task and enhancement requests in addition to defect reports.		bugs.sugarlabs.org will take task and enhancement requests in addition to defect reports.
	Forcing users to rename their USB sticks something esoteric like FEDORA is just wrong -->		Forcing users to rename their USB sticks something esoteric like FEDORA is just wrong -->
			<br><br>

	<!--I'd prefer something more legible than white text on white background when entering secret codes. -->		<!--I'd prefer something more legible than white text on white background when entering secret codes. -->
	*BootHelperCD cannot boot Mac without typing secret code into difficult to read window:<br> ''~~See~~ [[#~~Boot Helper~~ \| ~~Boot Helper~~ ]]~~... "If your boot hangs..." for complete details~~''		*BootHelperCD cannot boot Mac without typing secret code into difficult to read window:<br> ''for complete details [[ Talk:SoaS_Blueberry_Instructions#Using_boot_helper_disk_with_blueberry_usb_on_intel_mac \| click here ]]''
	<!--See the end of this discussion, http://answers.edge.launchpad.net/soas/+question/95622. It provides a way to edit the boot kernel arguments to boot on a Mac. You may be able to advance the instructions from there. -->		<!--See the end of this discussion, http://answers.edge.launchpad.net/soas/+question/95622. It provides a way to edit the boot kernel arguments to boot on a Mac. You may be able to advance the instructions from there. -->
	** interrupt the boot sequence		** press the tab key to interrupt the boot sequence.
	** append selinux=0 to the kernel's list of boot parameters.		** append selinux=0 to the kernel's list of boot parameters.
	** press return or enter to continue the boot process.		** press return or enter to continue the boot process.
	Submit bugs to request a different flavor of boot helper CD that boots Mac automatically, without typing selinux=0<!-- and removes the countdown, Macs innately have the option key interrupt, the mouse down interrupt and the power button interrupt to handle this boot time issue.-->		Submit bugs to request a different flavor of boot helper CD that boots Mac automatically, without typing selinux=0<!-- and removes the countdown, Macs innately have the option key interrupt, the mouse down interrupt and the power button interrupt to handle this boot time issue.-->
	<br>		<br>
	*BootHelperCD will not boot sticks created by a Mac.		*BootHelperCD will not boot sticks created by a Mac:
	** BootHelperCD can only boot sticks named FEDORA.		** BootHelperCD can only boot sticks named FEDORA.
	** Image-writer-mac writes the name blueberry-2-soas onto the stick.		** Image-writer-mac writes the name blueberry-2-soas onto the stick.
Line 155:		Line 156:
	This is a showstopper.<br>You cannot boot without hacking the USB stick name.<br>Use windows instructions to create Sugar on a Stick, named FEDORA, with persistent overlay.		This is a showstopper.<br>You cannot boot without hacking the USB stick name.<br>Use windows instructions to create Sugar on a Stick, named FEDORA, with persistent overlay.
	<br>		<br>
	*Sugar on a Stick is READ-ONLY		*Sugar on a Stick is READ-ONLY when created by a Mac:
	**Nothing is saved between reboots. Sugar asks for your name and colors each boot.		**Nothing is saved between reboots. Sugar asks for your name and colors each boot.
	**image-writer-mac does not create a persistent overlay file.		**image-writer-mac does not create a persistent overlay file.