Changes

This method of backup has the advantage that it copies Learner changes to the core operating system as well as the Journal.

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.

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.

 

An overarching vision is to be able to use and share Learners' Sugar environment wherever there are computing devices (see [[Sugar_on_a_Stick/Resources|Project Essence and Core Challenges]].)  Sugar then becomes a platform for continuous learning.  Working out the technical and social challenges of near-instantly resumable and portable learning with software is our challenge.  The separation of the system and Learner's Journal and Activities opens more opportunities for simpler solutions.

====See also====

====See also====

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.

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:==

==Needs and future:==

# More review and testing.

# More review and testing.

  -t designates the temporary directory to use,

  -t designates the temporary directory to use,

  -i designates files from the outer USB device's filesystem to include in the build.

  -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]"}})

     (Multiple files may be included with this syntax: -i "/f1, /d/f2, /d[/d.../f3]")

  -r designates releasefile names in the image that may need adjustment,

  -r designates releasefile names in the image that may need adjustment,

  --builder names the builder,

  --builder names the builder,

: (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.)

: (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 <u>that was installed with a {{Code|home.img}}</u>, then the home folder does not need to be transferred. The following commands will will refresh the overlay and system image:

If one only wants to refresh the source Live USB stick, then the home folder does not need to be transferred. The following commands 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.

* 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:

* From a root user Terminal activity or console session, issue this installation command:

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

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

If the source Live USB was installed without a separate {{Code|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.

If the source Live USB was installed without a separate {{Code|home.img}}, 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.  Even deleting Activities will consume more of the storage! (See [[LiveOS image]].) Because the home folder (Learner's Journal and Activities) are mixed into the system SquashFS image file in this configuration, that portfolio as a whole will be less easily swapped or shared from one device or machine to another.

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

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