Sugar on a Stick/Sugar Clone: Difference between revisions

Line 161:

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

#: <code>/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</code>

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

<nowiki> -n names the remix,

~~#:*:~~ (Multiple files may be included with this syntax: {{Code|-i "/f1, /d/f2, /d[/d.../f3]"}})

-o designates the output file location,

#:* -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 ~~{{Code|~~/dev/live}} partition (the currently running image).

-t designates the temporary directory to use,

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

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

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

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

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

-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).</nowiki>

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>

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

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

*: {{Code|/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}}.

@@ Line 161: / Line 161: @@
 # I invoked ''edit-liveos'' (saved as edit-liveos.py) with this command line:
 #: <code>/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</code>
-#:* -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.
+ <nowiki> -n names the remix,
-#:*: (Multiple files may be included with this syntax: {{Code|-i "/f1, /d/f2, /d[/d.../f3]"}})
+ -o designates the output file location,
-#:* -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 {{Code|/dev/live}} partition (the currently running image).
+ -t designates the temporary directory to use,
-# The script will launch and spew the files being copied to the screen and the progress of the rebuilding process.
+ -i designates files from the outer USB device's filesystem to include in the build.
-# 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>
+    (Multiple files may be included with this syntax: {{Code|-i "/f1, /d/f2, /d[/d.../f3]"}})
-#* 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.
+ -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).</nowiki>
+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>
+* 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.
+: (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
+*:  {{Code|/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}}.