Changes

Jump to navigation Jump to search
m
revised sh script for soas-v2-blueberry.iso
Line 1: Line 1:  +
=With the soas-2-blueberry.iso, leave out the 3 options for a separate persistent home:=
 +
*The older version of the script, shown below, will complete successfully, but the new installation startup process will have trouble finding the home folder and fail to complete.
 +
*Use this script for soas-v2-Blueberry.iso: (/dev/sd(x)1 is your USB device) use partition manager to determine what it is.
 +
 +
    sudo ./livecd-iso-to-disk.sh --overlay-size-mb 200  soas-2-blueberry.iso /dev/sd(x)1
 +
 +
=Older versions of SOAS:=
 +
\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 --home-size-mb NNN 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 leaving out the --home-size-mb NNN option).
 
*  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.  
   −
     sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-strawberry.iso /dev/sdb1
+
     sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-strawberry.iso /dev/sd(x)1
 
  −
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 --home-size-mb NNN 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 leaving out the --home-size-mb NNN option).
      
* The --delete-home option is used to avoid an error message while requesting both a new home (with --home-size-mb) and a persistent home (indirectly with --unencrypted-home). You wouldn't use the --delete-home option on an upgrade of the operation system only.  
 
* The --delete-home option is used to avoid an error message while requesting both a new home (with --home-size-mb) and a persistent home (indirectly with --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 --overlay-size-mb and --home-size-mb values (for example, for a 1-GB stick, use 200 for each).
 
Depending on the size of your USB stick, you may have to decrease --overlay-size-mb and --home-size-mb values (for example, for a 1-GB stick, use 200 for each).
  −
* If you get an error about udevinfo, you have the new version of udev where "udevadm info" is the proper command.
  −
  −
Create an executable file called udevinfo somewhere in your path with the following contents:
  −
  −
            #!/bin/bash
  −
            udevadm info $*
      
* Watch out for errors in the output of the script, the script seems to ignore them! (and say all is fine on the last line).
 
* Watch out for errors in the output of the script, the script seems to ignore them! (and say all is fine on the last line).
   −
copied from: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Linux
+
copied and revised from: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Linux
12,355

edits

Navigation menu