Sugar Creation Kit: Difference between revisions

Line 244:

: '''customize or duplicate Live USB installations'''

: (script files for making a customized Live USB installation self-replicating)

* ~~SugarCloneREADMEFIRST.pdf~~ [[Sugar on a Stick/Sugar Clone]]

* Sugar Clone http:~~//people~~.~~sugarlabs~~.~~org/fgrose/SugarClone~~

* '''SugarClone Wiki Page'''[[Sugar on a Stick/Sugar Clone]]

* Sugar Cellar, ~~script to report on disk space~~ in ~~[[LiveOS~~ image~~]]s~~

*: included in Sugar Clone

=====Possible Use Cases=====

*: or ~~available separately at http:~~/~~/people~~.~~sugarlabs~~.~~org/fgrose/SugarCellar~~

(from Wiki Page)

:'''Curriculum packaging'''

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

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

(such as a Physics model template or Etoys project), even saving distributable ebooks, or bookmarks in Browse Activity instances that are named for specific sets of local web destinations

(a class portal perhaps for deployments lacking Internet connectivity).

3. The teacher scrubs out any personal passwords or other history that should not be shared in the new copies.

4. A fresh or recycled USB stick is inserted into the computer running the customized SoaS image and the SugarClone script is executed.

:'''Full image backup or sharing'''

1. A Learner has modified their environment, perhaps adding Activity bundles and prepared specific instances such as a Activities/Physics simulation.

2. Their modifications include changes to their operating system installed through yum or RPM to obtain some new core functionality.

3. The Learner wants to archive or share this image with friends or for a backup.

4. Personal or private information is scrubbed from the Journal or Browse history and other potential stores.

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

=='''Build Your Own Remix''' ==

@@ Line 244: / Line 244: @@
 : '''customize or duplicate Live USB installations'''
 : (script files for making a customized Live USB installation self-replicating)
-* SugarCloneREADMEFIRST.pdf [[Sugar on a Stick/Sugar Clone]]
-* Sugar Clone http://people.sugarlabs.org/fgrose/SugarClone
+* '''SugarClone Wiki Page'''[[Sugar on a Stick/Sugar Clone]]
-* Sugar Cellar, script to report on disk space in [[LiveOS image]]s
-*: included in Sugar Clone
+=====Possible Use Cases=====
-*: or available separately at http://people.sugarlabs.org/fgrose/SugarCellar
+(from Wiki Page)
+:'''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.
+. 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
+    (such as a Physics model template or Etoys project), even saving distributable ebooks, or bookmarks in Browse Activity instances that are named for specific sets of local web destinations
+    (a class portal perhaps for deployments lacking Internet connectivity).
+. The teacher scrubs out any personal passwords or other history that should not be shared in the new copies.
+. A fresh or recycled USB stick is inserted into the computer running the customized SoaS image and the SugarClone script is executed.
+:'''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 yum or 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.
 =='''Build Your Own Remix''' ==