Sugar on a Stick/Sugar Clone

la versión revisada español

• Latest news: An alpha version of a python script that allows one to rebuild a custom iso image from a running image by 1.) staging the build on an attached hard drive and then 2.) copy only the content already on the current image. See http://www.mail-archive.com/soas@lists.sugarlabs.org/msg02044.html 28 January 2011 See #edit-liveos.py below.

Introduction

Sugar Clone makes it easy to share your personally-customized version of Sugar on a Stick.

1. Start with a fresh install of Sugar on a Stick (or use your current or favorite working image).

   (For greatest flexibility and reliability, use the livecd-iso-to-disk option, --home-size-mb NNN )

2. Add Activities, change Home favorites, save Browse bookmarks, Etoys projects, Physics model templates, download distributable ebooks, ... ...
3. Plug in a second, target USB/SD stick.
4. Switch to the Terminal Activity and execute 3 simple commands.

Voilà, you have a Sugar Clone! And the Sugar Clone can make new Sugar Clones with just 1 simple, Terminal command.

Some technicalities

Sugar Clone is, at this point in time, a Bash script (August 2010) that aids in the copying of a customized LiveOS image, such as Sugar on a Stick, to a secondary device. It works from within a booted LiveOS image to copy that image. Or it may be used to copy a LiveOS image between 2 attached USB/SD storage devices. It is intended to support the Sugar customization kit projects.

A small, utility script, Sugar Cellar, is available in the bundle, or separately. It is used to report on the storage space available on the persistent overlay, home directory, and other file spaces attached to the running image.

• http://people.sugarlabs.org/fgrose/SugarClone
• http://people.sugarlabs.org/fgrose/SugarCellar

A python script (alpha version) has been added in January 2011 that uses an attached hard drive to stage the creation of a new iso image installation file of the running SoaS instance. This permits system overlay refreshing and easy distribution of customized images.

• See this posting, http://www.mail-archive.com/soas@lists.sugarlabs.org/msg02044.html

See this announcement post,

You scream, I scream, we all scream for Mirabelle ice cream in a Sugar Clone.

And this follow-on discussion thread,

[SugarClone] -was: You scream, I scream, ....

Most recent post:

Application

• See the embedded help documentation in the script displayed below.

Test Usage

Pre-boot installation option:

1. Obtain the SugarClone script at http://people.sugarlabs.org/fgrose/SugarClone.
2. 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).

Boot:

Boot the computer from the USB stick into SoaS, and insert, or have a second USB device inserted, into the computer.

Clone:

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 for selection of 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.

Live USB installation option

On a running LiveOS image, the root folder of the parent USB/SD device is available at the /mnt/live mount point. The SugarClone script can be obtained (assuming Internet connectivity) as follows:

In the Terminal Activity ,
change the working directory:

cd /mnt/live

Get the SugarClone script file:

wget http://people.sugarlabs.org/fgrose/SugarClone

Clone:

SugarClone

Possible Use Cases

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.

See also

• Other neat uses for the modified_livecd-iso-to-disk script.

Notes

These scripts have been tested with SoaS-Mirabelle (available at http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/) but should work with other versions of SoaS.

The current version of the script has 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, the script will show a lot of output on the screen as it runs.

The script is copied to any new Sugar Clone devices prepared with this script so that Sugar Clone images can easily propagate themselves. This also applies to all new SoaS installations that are prepared with these scripts.

Needed:

1. More review and testing.
   • SD cards

ONE PROBLEM on Acer Aspire One 532H:
"Turns out the SD adapter uses the PCIe bus"
and is not recognized by Sugar or your Script
anyway to detect this in the script? (It is being used in test deployments now.)
The SD slot is NOT bootable on this model but could be used to make clone custom SD's for use on other netbooks (EeePC900)
satellit 04/26/2010

1. Submission of the modified_livecd-iso-to-disk script upstream.
   • https://bugzilla.redhat.com/show_bug.cgi?id=448030
2. Modifications for XOs.
3. Modifications for Intel Macintosh computers.
   • https://answers.edge.launchpad.net/soas/+question/95622
4. Extraction of the Learner's Sugar image name for labeling the Clone. (available 14 April 2010)
5. A Sugar Activity that calls or controls the scripts. See Activities/Toaster.
6. A way to automatically identify extra partitions on devices with more than one available partition.
7. A way to automatically identify live media images on secondary devices and partitions that could be used as sources for a Sugar Clone.
8. Bundling of the scripts for convenience until they are included in SoaS. (available 23 April 2010)
9. Extend the capability to write iso image files to refresh the SoaS installation with an empty system overlay.
   • See this comment https://bugzilla.redhat.com/show_bug.cgi?id=448030#c27
10. Write custom iso images for inexpensive distribution of CD-ROMs of the custom curriculum.
11. Extend the facility to any Sugar image.

These all should help us better prepare a SoaS customization kit.

Source

Sugar Clone

The script is available at http://people.sugarlabs.org/fgrose/SugarClone and is displayed from there below.
Embedded help, which describes the script and its usage in greater detail, is available in the script below (after the stock headers, click 3 to 5 times in the vertical scroll bar and look for 'shortusage()' and then the more complete 'usage()' functions).

http://people.sugarlabs.org/fgrose/SugarClone

Sugar Cellar

http://people.sugarlabs.org/fgrose/SugarCellar

Bundle

http://people.sugarlabs.org/fgrose/bundle

Launcher

http://people.sugarlabs.org/fgrose/launcher

edit-liveos.py

• The edit-liveos script can be thought of as a "liveos-disk-to-iso" script. It takes the currently installed system and converts it back into an iso9660 image file—but with all the current customizations to the system and Learner files.
• It is recommended that you use a separate, home.img file for the Learner's /home/liveuser directory to maximize your "mileage" with the consumable storage in the system overlay file.
  • This installation variation is only available currently from the livecd-iso-to-disk script packaged on the installation iso at either /LiveOS/ or /mnt/live/LiveOS/ (from inside a running installation) or, in standard Fedora LiveOS Spins, in /LiveOS/ in the device's outer filesystem (this is equivalent to /mnt/live/LiveOS/ from within the running installation).
  • livecd-iso-to-disk uses the --home-size-mb NNN options to specify the home.img installation.
• With edit-liveos (disk-to-iso), a nearly-consumed overlay can be refreshed by rebuilding the system into a new, SquashFS image that resparses the system files and repackages them into an iso installation file for reuse or distribution.

Usage

This is my recipe:

1. Having used the livecd-iso-to-disk with --home-size-mb NNN to install my SoaS iso onto a Live USB device, I proceed to customize my working Stick with new Activites, content, or system settings as described above in step 2.
2. I copy edit-liveos.py onto the USB device bearing SoaS (to the /LiveOS/ folder on the device's filesystem).
3. Before running the edit-liveos script, I run these 2 system updates:
   • yum install rsync
   • yum update livecd-tools
4. I boot my Sugar Stick on a system with a hard disc bearing an ext4-formatted partition with well over 5 GiB of free space.
5. Once booted, I mount the partition from a Terminal activity with the root user account:
   • su -
   • mount /dev/sdb2 /mnt/ext4

     (The device node and mountpoint names will depend on your resource names. You might find the device node by issuing df -Th or cat /proc/partitions and knowing something about your disc resources.)

6. I invoked edit-liveos (saved as edit-liveos.py) with this command line:

   /mnt/live/LiveOS/edit-liveos.py -n SoaSremix -o /mnt/ext4 -t /mnt/ext4 -i /GPL -r /boot/olpc-build --builder fgrose --clone /dev/live

 -n names the remix,
 -o designates the output file location,
 -t designates the temporary directory to use,
 -i designates files from the outer USB device's filesystem to include in the build.
    (Multiple files may be included with this syntax: {{Code|-i "/f1, /d/f2, /d[/d.../f3]"}})
 -r designates releasefile names in the image that may need adjustment,
 --builder names the builder,
 --clone flags the cloning feature to be invoked by the script on the
 /dev/live device partition (the currently running image).

The script will launch and spew the files being copied to the screen and the progress of the rebuilding process.

After about 20 minutes (on my system) the product iso file will be ready in the file, /mnt/ext4/SoaSremix-x86_64-YYYYMMDD.HH.iso

• This iso holds, in the /LiveOS/ directory, the home.img from the booted Live USB Stick, and fresh squashfs.img osmin.img files.

The livecd-iso-to-disk script should be used to install the new build, but it currently doesn't propagate a home.img file from the iso, so you will have to manually move the home.img file to the /LiveOS/ folder of a new USB device.

(With a GNU/Linux system, the iso image file can be auto-mounted in Nautilus and one can see the file to copy in the /LiveOS/ folder under the iso-image device.)

If one only wants to refresh the source Live USB stick that was installed with a home.img, then the home folder does not need to be transferred. The following commands will will refresh the overlay and system image:

• Boot into another image (such as from another SoaS device) with the target SoaS device inserted into a second USB connection port.
• From a root user Terminal activity or console session, issue this installation command:

  /path/to/livecd-iso-to-disk --overlay-size-mb NNN --unencrypted-home /path/to/refreshed/image.iso /dev/sd?1

• One needs to determine the proper paths on the working systems (for example, on a booted Mango Lassi, the path is /LiveOS/livecd-iso-to-disk.

If the source Live USB was installed without a separate home.img, then the above commands will also refresh your image, but it will consume the overlay more rapidly as all Activity storage is in the write-once overlay storage.

(Some of the above statements need to actually be tested. So please do so.)

The script code is below:

http://people.sugarlabs.org/fgrose/edit-liveos