SoaS Blueberry Instructions: Difference between revisions

(8 intermediate revisions by 3 users not shown)

Line 12:

|valign=top|

# 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).

# 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.

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.

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

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.

== 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.

Line 52:

* 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'''

Line 62:

* 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 ==

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

{{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]].}}

''Sugar on a Stick Blueberry and Strawberry images are for the Intel processor.''

''See [[#Older Mac with powerPC processor | Using Sugar with powerPC]] if you do not have an Intel processor.''

* See also [[Macintosh]].

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

Line 102:

Line 105:

'''To install Sugar onto a Stick'''

* Download the [http://download.sugarlabs.org/soas/releases/image-writer-mac image-writer for Mac ~~computers~~ ] ~~(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).~~ ~~Verify the file was downloaded properly ''by calculating its [http://download.sugarlabs.org/soas/releases/SHA1SUM SHA-1 checksum]'' 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 ] ''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]'' 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. '''WARNING:''' your entire flash drive will be overwritten in the next step! All partitions will be erased.

Line 118:

Line 123:

'''To create a Boot Helper CD'''

* Download the USB boot helper [http://download.sugarlabs.org/soas/releases/soas-2-boot.iso soas-2-boot.iso]~~ ~~Verify the file was downloaded properly ''by calculating its [http://download.sugarlabs.org/soas/releases/SHA1SUM SHA-1 checksum]'' 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]'' 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.

* Insert a blank disc when prompted.

Line 132:

Line 138:

**you may release the c key once the sugar logo appears.

===Suggestion: ~~Using boot_helper_disk_with_blueberry_usb_on_intel_mac~~===

===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 ~~Boot~~ Bugs ====

''The boot sequence does not work properly due to minor bugs. Follow these workarounds to boot an intel Mac.'' ''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'' ''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.

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.

*BootHelperCD cannot boot Mac without typing secret code into difficult to read window: ''for complete details [[ Talk:SoaS_Blueberry_Instructions#Using_boot_helper_disk_with_blueberry_usb_on_intel_mac | click here ]]''

-->

** press the tab key to interrupt the boot sequence.

*~~image-writer-mac~~ and BootHelperCD ~~are~~ not ~~compatible~~:

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

*BootHelperCD will not boot sticks created by a Mac:

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

This is a showstopper. You cannot boot without hacking the USB stick name. Use a windows ~~machine~~ to create Sugar on a Stick, named FEDORA, with persistent overlay.

This is a showstopper. You cannot boot without hacking the USB stick name. Use windows instructions to create Sugar on a Stick, named FEDORA, with persistent overlay.

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

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

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

@@ Line 12: / Line 12: @@
 |valign=top|
 # 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).
 # 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.
@@ 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.
-::# 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:
@@ 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.
-== For GNU/Linux Users ==
+== For GNU/Linux users ==
--)Linux Users will use a slightly different approach than Windows Users to ensure maximum compatibility
+. 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.
@@ Line 52: / Line 52: @@
 * Launch LiveUSB Creator and follow the instructions [[SoaS_Blueberry_Instructions#For_Windows_Users|above]].
--)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].
+. 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'''
@@ Line 62: / Line 62: @@
 * You will be notified once the process has finished.
--)'''zyx-liveinstaller:'''[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/ZyX-LiveInstaller]
+. '''zyx-liveinstaller:''' [[Sugar on a Stick/ZyX-LiveInstaller]]
--)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]
+. '''Instructions for installing with persistent storage for Blueberry: ''' [[Talk:SoaS Blueberry Instructions]]. See also [[Sugar on a Stick/Linux]].
 == 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 ==
+{{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]].}}
 ''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 also [[Macintosh]].
 ====To identify the Mac's processor and OS X version====
@@ Line 102: / Line 105: @@
 '''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.
@@ Line 118: / Line 123: @@
 '''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.
 * Insert a blank disc when prompted.
@@ Line 132: / Line 138: @@
 **you may release the c key once the sugar logo appears.
-===Suggestion: Using boot_helper_disk_with_blueberry_usb_on_intel_mac===
+===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  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.
-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 -->
+<br><br>
-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> ''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. -->
+** press the tab key to interrupt the boot sequence.
-*image-writer-mac and BootHelperCD are not compatible:
+** 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.
-** 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.
-  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 when created by a Mac:
 **Nothing is saved between reboots. Sugar asks for your name and colors each boot.
 **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====