On Thu, May 13, 2010 at 12:19 AM, Frederick Grose <fgr...@gmail.com> wrote: > > A minor update to Sugar Clone, a tool to clone a customized ...
Another small update is available for Sugar Clone, a tool to clone a customized Sugar on a Stick installation onto another USB stick. http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone <http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone> Available at: http://people.sugarlabs.org/fgrose/SugarClone. New: 1. Ignore empty USB device ports (that showed up on some USB device hubs). 2. Abstracted out script launching from the bundle-building script. 3. Show a leading zero for device storage capacities less than 1 GiB. 4. Some minor code simplification. Test Usage: 1. Before booting the SoaS device that will be the source of the new Sugar Clone, copy the SugarClone script to the root, '/', folder at the base of the filesystem for the device, or, to /mnt/live (from the perspective of a running LiveOS image). 2. Boot the computer from the USB stick into SoaS, and insert, or have a second USB device inserted, into the computer. 3. In the Terminal Activity of that running SoaS image, enter the command, /mnt/live/SugarClone If there is more than one USB/SD storage device available, a menu of the devices will appear allowing you to select the target device. The scripts will copy the currently running image to the target device. When that device is booted, a new, Sugar Learner sign-in will be triggered. The previously customized Journal and operating system will be present on the Sugar Clone. On a running LiveOS image, the root folder of the USB/SD device is available at the /mnt/live mount point. The SugarClone script can be obtained (assuming Internet connectivity) as follows: 1. In the Terminal Activity, change the working directory: cd /mnt/live 2. wget http://people.sugarlabs.org/fgrose/SugarClone 3. chmod +x SugarClone at this point, you may simply execute SugarClone See http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone for more information. Notes: See http://wiki.sugarlabs.org/go/LiveOS_image for more information on optimizing file storage for LiveOS images. Information and suggestions there may be particularly relevant for SoaS deployments that want to use the stock LiveOS installation with greater capacity for Activity storage with a longer lifetime for the write-once, persistent overlay. See also the http://wiki.sugarlabs.org/go/Activities/Toaster project, which aims to make a graphical Sugar Activity for cloning Sugar images. --Fred
_______________________________________________ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
