Sugar on a Stick/Sugar Clone: Difference between revisions

Line 5:

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

* '''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.

Line 167:

# 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>

#* 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.

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

* 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 {{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.

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

The script code is below:

@@ Line 5: / Line 5: @@
-* '''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'''
+* '''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.
@@ Line 167: / Line 167: @@
 # 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>
 #* 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.
+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 <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:
+* 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 {{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.
+(Some of the above statements need to actually be tested. So please do so.)
 The script code is below: