Changes

: {{Code|chmod +x livecd-iso-to-disk.sh}}

: {{Code|chmod +x livecd-iso-to-disk.sh}}

* Run it as root, making sure to pass the correct USB device and to set overlay and home size appropriately, depending on the stick size.

* Run it as root, making sure to pass the correct USB device and to set overlay and home size appropriately, depending on the stick size.

: {{Code|sudo ./livecd-iso-to-disk.sh --reset-mbr --overlay-size-mb 300 --home-size-mb 200 --delete-home --unencrypted-home /path/to/SoaS.iso /dev/sd''b1''}}

: {{Code|sudo ./livecd-iso-to-disk.sh --reset-mbr --overlay-size-mb 300 --home-size-mb 175 --delete-home --unencrypted-home /path/to/SoaS.iso /dev/sd''b1''}}

:: '''Note:''' With the soas-2-blueberry.iso, leave out the 3 options for a separate persistent home.  The script will complete successfully, but the new installation startup process will have trouble finding the home folder and fail to complete.

:: '''Note:''' With the soas-2-blueberry.iso, leave out the 3 options for a separate persistent home.  The script will complete successfully, but the new installation startup process will have trouble finding the home folder and fail to complete.

:: Normally, the ''livecd-iso-to-disk'' installation has the advantage over the ''liveusb-creator'' installation method by allowing a persistent /home/liveuser folder with the <tt>--home-size-mb ''NNN''</tt> option. This feature would allow you to update the OS image while keeping the user files (by running the script against your existing installation but <u>leaving out</u> the --home-size-mb NNN option).

:: Normally, the ''livecd-iso-to-disk'' installation has the advantage over the ''liveusb-creator'' installation method by allowing a persistent /home/liveuser folder with the <tt>--home-size-mb ''NNN''</tt> option. This feature would allow you to update the OS image while keeping the user files (by running the script against your existing installation but <u>leaving out</u> the --home-size-mb NNN option).

::* The {{Code|--delete-home}} option is used to avoid an error message while requesting both a new home (with {{Code|--home-size-mb}}) and a persistent home (indirectly with {{Code|--unencrypted-home}}). You wouldn't use the --delete-home option on an upgrade of the operation system only.

::* The {{Code|--delete-home}} option is used to avoid an error message while requesting both a new home (with {{Code|--home-size-mb}}) and a persistent home (indirectly with {{Code|--unencrypted-home}}). You wouldn't use the --delete-home option on an upgrade of the operation system only.

:Depending on the size of your USB stick, you may have to decrease {{Code|--overlay-size-mb}} and {{Code|--home-size-mb}} values (for example, for a 1-GB stick, use 300 for the overlay and 200 for the home folder).

:Depending on the size of your USB stick, you may have to decrease {{Code|--overlay-size-mb}} and {{Code|--home-size-mb}} values (for example, for a 1-GB stick, use 300 for the overlay and 175 for the home folder).

:: If you have sufficient capacity on your target device, and format it with an ext[234] filesystem to overcome the 2048-MB fat32 file size limit, you may avoid the SquashFS compression by including the {{Code|--skipcompress}} option in the script command line.

:: If you have sufficient capacity on your target device, and format it with an ext[234] filesystem to overcome the 2048-MB fat32 file size limit, you may avoid the SquashFS compression by including the {{Code|--skipcompress}} option in the script command line.

<!--:* If you get an error about udevinfo, you have the new version of udev where "udevadm info" is the proper command.

<!--:* If you get an error about udevinfo, you have the new version of udev where "udevadm info" is the proper command.