<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Fred; Used new SugarClone loaded by itself into USB: (Drag drop into opened USB on Ubuntu 9.04 desktop) Then Booted Acer Aspire One with it.) sugar-terminal: ---------------------------------------------------------------------- [liveuser@localhost ~]$ /mnt/live/SugarClone          clone options:     installer options:       This Live USB/SD device was detected:          usb..Lexar..JD FireFly../dev/sdb../mnt/live..LIVE..1.9-GiB       One USB/SD storage device is available:          usb..Lexar..JDFireFly../dev/sdc../media/LIVE..LIVE..1.9-GiB             That's where we'll load the SugarClone.          /dev/sdc1       Source is on a vfat partition.    Builder: soas-426    Updating boot config file.      There is 89.7 % of the 1200 MiBytes in LiveOS    persistent storage that is free on both the Source & Target devices.      Calling:    /tmp/modified_livecd-iso-to-disk --noverify --copy-overlay --delete-home --copy-home  /dev/live /dev/sdc1   Already set up as live image. Deleting old OS in fifteen seconds... Copying live image to USB stick Copied overlay. Updating boot config file Installing boot loader USB stick set up as live image!      Cleaning up to exit...    Waiting for devices to settle...      Done... You may use your Sugar Clone now!   [liveuser@localhost ~]$ ------------------------------------------------------ Cloned Custom USB works fine. Opens up with Sugar "Name" screen Remembers wireless login Has contents of journal from master USB (the modified script is added to /mnt/live after running SugarClone script.) Tom Gilliard satellit Frederick Grose wrote: <blockquote cite="mid:i2qf3383f811004261837rd721de11ib91a5906529a51df@mail.gmail.com" type="cite"> <pre wrap="">On Fri, Apr 23, 2010 at 1:48 AM, Frederick Grose <a class="moz-txt-link-rfc2396E" href="mailto:fgrose@gmail.com"><fgrose@gmail.com></a> wrote: Not yet final, but ready for more testing is a new version of SugarClone, </pre> <blockquote type="cite"> <pre wrap=""><a class="moz-txt-link-freetext" href="http://people.sugarlabs.org/fgrose/SugarClone">http://people.sugarlabs.org/fgrose/SugarClone</a>. </pre> </blockquote> <pre wrap=""> </pre> <pre wrap=""> New: </pre> <pre wrap="">1. Reports the portion of persistent overlay or home folder storage that remains on the file systems. This will help Learners manage their storage resources and learn ways to economize limited resources. (See notes below.) 2. Uses the /tmp/ directory, which is on a RAM file system in LiveOS images, to run the installation scripts and save temporary mount points and files. This conserves the write-once persistent over- lay 2. Bug fixes a. Allows multiple options to be entered. b. Improved support for cloning from one attached device to another. Test Usage: </pre> <pre wrap="">1. Before booting the SoaS device that will be the source of the new </pre> <blockquote type="cite"> <pre wrap=""> SugarClone, copy the SugarClone script to the root '/' folder at </pre> </blockquote> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap=""> the base of the filesystem for the device or to /mnt/live (from </pre> </blockquote> <pre wrap=""> the perspective of a running LiveOS image). </pre> <pre wrap="">2. Boot the USB stick into SoaS and insert a second USB device into the computer running that SoaS image. </pre> <pre wrap="">3. In the Terminal Activity of that running SoaS image, enter the </pre> <blockquote type="cite"> <pre wrap=""> command, </pre> </blockquote> <pre wrap=""> </pre> <pre wrap=""> /mnt/live/SugarClone </pre> <pre wrap="">If there is more than one USB/SD storage device available, a menu of the devices will appear for selection of the target device. </pre> <pre wrap="">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 SugarClone image. </pre> <pre wrap="">On a running LiveOS image, the root folder of the USB/SD device is </pre> <blockquote type="cite"> <pre wrap="">available at the /mnt/live mount point. The SugarClone script </pre> </blockquote> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">can be obtained (assuming Internet connectivity) as follows: </pre> </blockquote> <pre wrap=""> </pre> <pre wrap="">1. In the Terminal Activity, change the working directory: </pre> <pre wrap=""> cd /mnt/live </pre> <pre wrap="">2. wget <a class="moz-txt-link-freetext" href="http://people.sugarlabs.org/fgrose/SugarClone">http://people.sugarlabs.org/fgrose/SugarClone</a> </pre> <pre wrap="">3. chmod +x SugarClone at this point, you may simply execute SugarClone </pre> <pre wrap=""> See <a class="moz-txt-link-freetext" href="http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone">http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone</a> for more information. </pre> <pre wrap=""> Notes: </pre> <pre wrap="">The Fedora LiveOS system allows for persistent storage in 3 ways: 1. A general persistent overlay - a compressed, write-once, fixed-size file space that will save updates and changes the LiveOS image (Activities, operating system changes, anything written in the LiveOS file space. 2. Persistent Home folder - a re-sizable (with difficulty), uncompressed, optionally-encryptable, file space for anything that goes in the Learner's /home/ folder (all the Sugar Activities, logs, and good stuff). 3. The device's original partition file space - outside of the LiveOS file tree, but accessible through the /mnt/live folder mount point. There, one will find the boot configuration files and anything else one had on the device before loading SoaS. Any file one might want to carry on the stick, without consuming the other limited file spaces, may be saved here (limited by device capacity). The standard persistent overlay is needed for operating system changes and updates. But, one may find many advantages to installing Sugar on a Stick with a persistent home folder (--home-size-mb NN --delete-home) that will hold all the Activities one wants to try and, perhaps later, throw away--all without consuming the write-once overlay that would fill up very quickly. Additionally, keeping some device disc storage space out of the LiveOS system will let you copy, carry, and delete large resource files, such as alternate image .iso files, or anything you might want to use or share. (We should adjust the Journal code to show this root mount to facilitate file sharing.) Sugar on a Stick may be installed on a 1-GB USB device using these options to livecd-iso-to-disk or modified_livecd-iso-to-disk: ./livecd-iso-to-disk --overlay-size-mb 200 --home-size-mb 200 \ --delete-home --unencrypted-home /path/to/source/iso/or/device \ /dev/sdA1 (where 'A' represents your bootable device node, such as sdb1 or sdc1, etc., and the backslashes '\' are line-continuation symbols.) That would allow space for the home folder, the operating system, and a little on the device root. But with a larger storage device, one can allocate the resources to suit the anticipated use as described above. The new feature that reports persistent file space usage on the LiveOS device is included as a component script in SugarClone. It is separately available, to allow for Learner testing and discovery, in the 'SugarCellar' script (saved in /mnt/live/LiveOS/SugarCellar. (Available at <a class="moz-txt-link-freetext" href="http://people.sugarlabs.org/fgrose/SugarCellar">http://people.sugarlabs.org/fgrose/SugarCellar</a>.) --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>