As requested in http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO, https://bugzilla.redhat.com/show_bug.cgi?id=448030, and http://bugs.sugarlabs.org/ticket/74, the following 3 scripts provide a testable means to duplicate a running SoaS image that may have been customized (in its persistent overlay or home folder):
modified_livecd-iso-to-disk transferSugarImage newSugarStick These are available at http://people.sugarlabs.org/fgrose/. Test Usage: 1. Copy the script files above to the root '/' folder at the base of the filesystem on a SoaS USB stick known to run Sugar. 2. Boot the USB stick into SoaS and insert a second USB device into the computer running that SoaS image. 3. In the Terminal Activity of that running SoaS image, enter the command, /mnt/live/newSugarStick (At this point in development, the transferSugarImage script assumes that the second device is mounted and recognized as /dev/sdc1. You may confirm this by executing the command, mount and checking for the lines that return your second device's name and device partition, such as /dev/sdc1.) 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, but the customized Journal and operating system will be present. Possible Use Case: 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, even saving bookmarks in Browse instances that are named for specific sets of web destinations. 3. The teacher scrubs out any personal passwords or other history that should not be shared in the new copies. 4. Following customization, a fresh or recycled USB stick is inserted into the computer running the customized SoaS image. 5. The Sugar Terminal Activity is opened and this command is entered: /mnt/live/newSugarStick Step 5 assumes that Usage step 1 has been performed either directly or by the SoaS packagers. Presently, the transferSugarImage script is hard-coded to run the modified_livecd-iso-to-disk installation script with these options: --noverify To avoid the need for verification software--a running image is its own form of verification. --copy-overlay This duplicates the customizations on the source image operating system, including those in the home folder if there was no separate, persistent home. --delete-home This is required to confirm deletion of a persistent home folder, if it exists on the target device. --copy-home This duplicates the customizations on the source image home folder, if it exists. The modified_livecd-iso-to-disk script has a new option, --help, which displays its usage instructions. These scripts have been tested with SoaS-Mirabelle (available at http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/). The scripts have have the /bin/bash shell specified with the -x (xtrace) option set to aid in testing. That means they will show a lot of output on the screen as they run. The scripts are copied to new SoaS devices prepared with these scripts so that they can propagate themselves. Needed: 1. Review and testing. 3. Submission of modified_livecd-iso-to-disk upstream 2. A way to determine the name of the secondary USB device partition automatically in the transferSugarImage script. 3. A Sugar Activity that calls the scripts. These steps should help us prepare a SoaS customization kit. --Fred
_______________________________________________ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
