8,288
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − + + + + + − + − + Line 26:
Line 30: − + − + Line 34:
Line 38: + + + + + + + + + Line 49:
Line 62: + + − + +
Sugar on a Stick/Sugar Clone (view source)
Revision as of 22:51, 13 April 2010
, 22:51, 13 April 2010no edit summary
Sugar Clone is, at this point in time (April 2010), a bash script that aids in the copying of a LiveOS live image, such as Sugar on a Stick, to a secondary device. It is intended to support the Sugar image customization kit projects.
Sugar Clone is, at this point in time (April 2010), a bash script that aids in the copying of a LiveOS live image, such as Sugar on a Stick, to a secondary device. It is intended to support the Sugar image customization kit projects.
See this announcement post, [http://www.mail-archive.com/soas@lists.sugarlabs.org/msg01018.html You scream, I scream, we all scream for Mirabelle ice cream in a Sugar Clone].
See this announcement post, <div class="NavFrame collapsed"><div class="NavHead">[http://www.mail-archive.com/soas@lists.sugarlabs.org/msg01018.html You scream, I scream, we all scream for Mirabelle ice cream in a Sugar Clone] </div><div class="NavContent">{{#widget:Iframe
|url=http://www.mail-archive.com/soas@lists.sugarlabs.org/msg01018.html
|width=900
|height=336
}}</div></div> .
==Introduction==
==Introduction==
* See the embedded help documentation in the script [[#Source|displayed below]].
* See the embedded help documentation in the script [[#Source|displayed below]].
===Test Usage:===
===Test Usage===
# Before booting the SoaS device that will be the source of the new SugarClone, copy the script files above to the root '/' folder at the base of the filesystem (not the /root folder).
# Before booting the SoaS device that will be the source of the new SugarClone, copy the script files above to the root '/' folder at the base of the filesystem (not the /root folder).
# Boot the USB stick into SoaS and insert a second USB device into the computer running that SoaS image.
# Boot the USB stick into SoaS and insert a second USB device into the computer running that SoaS image.
# In the Terminal Activity of that running SoaS image, enter the command,
# In the Terminal Activity of that running SoaS image, enter the command,
#: <code>/mnt/live/SugarClone</code>
#: <big><code>/mnt/live/SugarClone</code></big>
The scripts will copy the currently running image to the second device. When the second device is booted, a new Sugar Learner sign in will be triggered, and the customized Journal and operating system will be present.
The scripts will copy the currently running image to the second device. When the second device is booted, a new Sugar Learner sign in will be triggered, and the customized Journal and operating system will be present.
: <code>chmod +x SugarClone</code>
: <code>chmod +x SugarClone</code>
</big>
</big>
===Possible Use Case:===
===Possible Use Cases===
====Curriculum packaging====
# A teacher wants to prepare a SoaS image with a custom set of installed Activity bundles or a Journal of Activity instances for an upcoming class term.
# A teacher wants to prepare a SoaS image with a custom set of installed Activity bundles or a Journal of Activity instances for an upcoming class term.
# The teacher modifies their current working image by adding or deleting Activity bundles from their Home view and adding or removing Journal entries with specific content, even saving distributable ebooks, or bookmarks in Browse instances that are named for specific sets of local web destinations (a class portal perhaps for deployments lacking Internet connectivity).
# The teacher modifies their current working image by adding or deleting Activity bundles from their Home view and adding or removing Journal entries with specific content, even saving distributable ebooks, or bookmarks in Browse instances that are named for specific sets of local web destinations (a class portal perhaps for deployments lacking Internet connectivity).
Step 4 assumes that Usage step 1 has been performed either directly or by the SoaS packagers.
Step 4 assumes that Usage step 1 has been performed either directly or by the SoaS packagers.
====Full image backup or sharing====
# A Learner has modified their environment, perhaps adding Activity bundles and prepared specific instances such as a [[Activities/Physics]] simulation.
# Their modifications include changes to their operating system installed through [[wikipedia:YUM|YUM]] or [[wikipedia:RPM (Computer)|RPM]] to obtain some new core functionality.
# The Learner wants to archive or share this image with friends or for a backup.
# Personal or private information is scrubbed from the Journal or Browse history and other potential stores.
# The User creates one or more Sugar Clones.
This method of backup has the advantage that it copies Learner changes to the core operating system as well as the Journal.
A LiveOS image using a separate persistent home folder could be partially cloned with either the operating system overlay or home folder without the other should that be desired.
===Notes===
===Notes===
# Modifications for XOs.
# Modifications for XOs.
# Modifications for Intel Macintosh computers.
# Modifications for Intel Macintosh computers.
# Extraction of the Learner's Sugar image name for labeling the Clone.
# A Sugar Activity that calls or controls the scripts.
# A way to automatically identify extra partitions on devices with more than one available partition.
# A way to automatically identify extra partitions on devices with more than one available partition.
# A way to automatically identify live media images on secondary devices and partitions that could be used as sources for a Sugar Clone.
# A way to automatically identify live media images on secondary devices and partitions that could be used as sources for a Sugar Clone.
# Bundling of the scripts for convenience until they are included in SoaS.
# Bundling of the scripts for convenience until they are included in SoaS.
# A Sugar Activity that calls or controls the scripts.
# Extend the capability to write CD-ROM image files for inexpensive distribution.
# Extend the facility to any Sugar image.
These all should help us better prepare a SoaS customization kit.
These all should help us better prepare a SoaS customization kit.