<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> I tested this but ran into problems: I selected /dev/sde1 as USB to write to but SugarClone script insisted on /dev/sdd for source USB - but my source live USB is /dev/sdc1. (EeePC900 with solid state drives which are seen) Need way to specify source and target USB in SugarClone command. (Or in script selection menu) (Unless I did not understand extended options) The old script works fine for me: /mnt/live/newSugarStick works with target edited to match "mount" command output.  (* edit the script :transferSugarImage line: TARGETDEV=/dev/sd(*) Where can this edit be done on new script? Tom Gilliard satellit Frederick Grose wrote: <blockquote cite="mid:q2jf3383f811004122305zd2042919g61b16a75c6324ba8@mail.gmail.com" type="cite"> <pre wrap="">Was: Duplicating SoaS with customization. New work: 1. Reduced the 3 earlier scripts to 2 that provide a means to duplicate a running SoaS image together with its customizations in a persistent overlay or home folder. modified_livecd-iso-to-disk SugarClone These are available at <a class="moz-txt-link-freetext" href="http://people.sugarlabs.org/fgrose/">http://people.sugarlabs.org/fgrose/</a>. 2. Automated detection of attached USB storage devices and provide a selection menu if there are more than one. 3. Maintained a simple command line for the default case: /mnt/live/SugarClone (even as the default liveuser account). 4. Provided input auditing for advanced uses. 5. Embedded a much more complete usage document available as an option: /mnt/live/SugarClone --help 6. Tested and updated more code paths. 7. Adopted satellit's suggestion to update the boot menu Welcome title. And updated the 'About my Computer' Build information so this is available at run time. Test Usage: 1. 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). 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/SugarClone 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. Step 1 above, from the perspective of the learner inside a currently running SoaS image, would be different: The root folder of the USB device would be reached through the /mnt/live mount point. The scripts could be obtained (assuming Internet connectivity) as follows: 1. In the Terminal Activity, change the working directory: cd /mnt/live 2. wget <a class="moz-txt-link-freetext" href="http://people.sugarlabs.org/fgrose/modified_livecd-iso-to-disk">http://people.sugarlabs.org/fgrose/modified_livecd-iso-to-disk</a> wget <a class="moz-txt-link-freetext" href="http://people.sugarlabs.org/fgrose/SugarClone">http://people.sugarlabs.org/fgrose/SugarClone</a> 3. chmod +x modified_livecd-iso-to-disk chmod +x SugarClone 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 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). 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 that is inserted into the computer running the customized SoaS image can become the SugarClone. Step 5 assumes that Usage step 1 has been performed either directly or by the SoaS packagers. These scripts have been tested with SoaS-Mirabelle (available at <a class="moz-txt-link-freetext" href="http://alt.pub/alt/nightly-composes/soas/">http://alt.pub/alt/nightly-composes/soas/</a><a class="moz-txt-link-rfc2396E" href="http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/"><http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/></a>) but should work with other versions of SoaS. The current version of the scripts have the /bin/bash shell specified without the -x (xtrace) option. Set this option, #!/bin/bash -x in the first line of the script to aid testing. When set, they will show a lot of output on the screen as they run. The scripts are copied to the new SugarClone devices prepared with these scripts so that they can easily propagate themselves. This also applies to all new SoaS installations that are prepared with these scripts (using --image <source> options). Needed: 1. More review and testing. 2. Submission of the modified_livecd-iso-to-disk script upstream. 3. Modifications for Intel Macintosh computers. 4. A way to automatically identify extra partitions on devices with more than one available partition. 5. A way to automatically identify live media images on secondary devices and partitions that could be used as sources for a SugarClone. 6. Bundling of the scripts for convenience until they are included in SoaS. 7. A Sugar Activity that calls the scripts. These all should help us better prepare a SoaS customization kit. --Fred </pre> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ SoaS mailing list <a class="moz-txt-link-abbreviated" href="mailto:SoaS@lists.sugarlabs.org">SoaS@lists.sugarlabs.org</a> <a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/soas">http://lists.sugarlabs.org/listinfo/soas</a> </pre> </blockquote> </body> </html>