8,288
edits
Changes
Jump to navigation
Jump to search
Line 125:
Line 125: − + − + + + Line 175:
Line 177: − + Line 184:
Line 186: − +
Sugar on a Stick/Sugar Clone (view source)
Revision as of 01:57, 30 January 2011
, 01:57, 30 January 2011no edit summary
# A way to automatically identify live media images on secondary devices and partitions that could be used as sources for a Sugar Clone.
# A way to automatically identify live media images on secondary devices and partitions that could be used as sources for a Sugar Clone.
# <s>Bundling of the scripts for convenience until they are included in SoaS.</s> (available 23 April 2010)
# <s>Bundling of the scripts for convenience until they are included in SoaS.</s> (available 23 April 2010)
# Extend the capability to write iso image files to refresh the SoaS installation with an empty system overlay.
# Write custom iso image files to refresh the SoaS installation with an empty system overlay and permit redistribution of the customized system iso. (available 28 January 2011)
#* See this comment https://bugzilla.redhat.com/show_bug.cgi?id=448030#c27
#* See this comment https://bugzilla.redhat.com/show_bug.cgi?id=448030#c27
# Write custom iso images for inexpensive distribution of CD-ROMs of the custom curriculum.
#* Add the ability to refresh the installation without restarting or re-installing.
# Extend the facility to any Sugar image.
# Extend the facility to any Sugar image.
# Allow Learner account/stick swapping without rebooting.
# Allow multi-architecture distributions for larger capacity devices.
These all should help us better prepare a SoaS customization kit.
These all should help us better prepare a SoaS customization kit.
The script will launch and spew the files being copied to the screen and the progress of the rebuilding process.
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, <code>/mnt/ext4/SoaSremix-x86_64-YYYYMMDD.HH.iso</code>
After about 10 minutes (on my system) the product iso file will be ready in the file, <code>/mnt/ext4/SoaSremix-x86_64-YYYYMMDD.HH.iso</code>
* This iso holds, in the <code>/LiveOS/</code> directory, the {{Code|home.img}} from the booted Live USB Stick, and fresh {{Code|squashfs.img osmin.img}} files.
* This iso holds, in the <code>/LiveOS/</code> directory, the {{Code|home.img}} from the booted Live USB Stick, and fresh {{Code|squashfs.img osmin.img}} files.
* 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:
*: {{Code|/path/to/livecd-iso-to-disk --overlay-size-mb NNN --unencrypted-home /path/to/refreshed/image.iso /dev/sd?1}}
*: {{Code|/path/to/livecd-iso-to-disk --overlay-size-mb NNN /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 {{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}}.