8,288
edits
Changes
Jump to navigation
Jump to search
Line 6:
Line 6: − + − + Line 29:
Line 29: − + Line 79:
Line 79: − + − + − + − + − #!/bin/bash+ − udevadm info $*+ − +
no edit summary
* See [[Sugar on a Stick/Installation/OLPC]] for booting an OLPC XO-1 with SoaS images.
* See [[Sugar on a Stick/Installation/OLPC]] for booting an OLPC XO-1 with SoaS images.
== Put SoaS as a vmware appliance onto a vmware player stick ==
== Put SoaS as a VMware appliance onto a VMware Player stick ==
[http://wiki.sugarlabs.org/go/VMware These instructions] will help you put a [[Sugar on a Stick#Downloading|SoaS image]] onto a USB
[http://wiki.sugarlabs.org/go/VMware These instructions] will help you put a [[Sugar on a Stick#Downloading|SoaS image]] onto a USB
stick that boots into VMPlayer that then runs a VMAppliance containing a [[Sugar on a Stick#Downloading|SoaS image]].
stick that boots into VMware Player that then runs a VMware Virtual Appliance containing a [[Sugar on a Stick#Downloading|SoaS image]].
== openSUSE SoaS variant ==
== openSUSE SoaS variant ==
:*''cryptsetup'' is only needed for the option to provide password protection and encryption for the persistent /home/liveuser folder. It is not necessary if one applies the recommended <code>--unencrypted-home</code> option. The <code>--unencrypted-home</code> option is preferred because the reduced overhead improves robustness with the compressed ''squashfs'' file system employed by the Live USB deployment.
:*''cryptsetup'' is only needed for the option to provide password protection and encryption for the persistent /home/liveuser folder. It is not necessary if one applies the recommended <code>--unencrypted-home</code> option. The <code>--unencrypted-home</code> option is preferred because the reduced overhead improves robustness with the compressed ''squashfs'' file system employed by the Live USB deployment.
* Plug in a 1GB or larger USB stick into your computer.
* Plug in a 1GB or larger USB stick into your computer.
* Download the installation script: http://people.sugarlabs.org/sdz/livecd-iso-to-disk.sh (09 April 2009)
* Download the installation script: http://download.sugarlabs.org/soas/releases/livecd-iso-to-disk.sh (23 June 2009).
* Check the USB device. In the example below the device is /dev/sdb:
* Check the USB device. In the example below the device is /dev/sdb:
* 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.
: <tt>sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-beta.iso /dev/sd''b1''</tt>
: <tt>sudo ./livecd-iso-to-disk.sh --overlay-size-mb 300 --home-size-mb 160 --delete-home --unencrypted-home soas-beta.iso /dev/sd''b1''</tt>
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 ''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</code> option is used to avoid an error message while requesting both a new home (with <code>--home-size-mb</code>) and a persistent home (indirectly with <code>--unencrypted-home</code>). You wouldn't use the --delete-home option on an upgrade of the operation system only.
::* The <code>--delete-home</code> option is used to avoid an error message while requesting both a new home (with <code>--home-size-mb</code>) and a persistent home (indirectly with <code>--unencrypted-home</code>). 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</code> and <code>--home-size-mb</code> values (example, for 1 GB stick, use 200 for each).
:Depending on the size of your USB stick, you may have to decrease <code>--overlay-size-mb</code> and <code>--home-size-mb</code> values (example, for 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:
:* 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:
:::<code>#!/bin/bash</code><br>
:::<code>udevadm info $*</code>
* Watch out for errors in the output of the script, the script seams to ignore them!(and say all is fine on the last line).
:* Watch out for errors in the output of the script, the script seams to ignore them! (and say all is fine on the last line).
===Transcript===
===Transcript===