8,288
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − + Line 41:
Line 41: − + Line 96:
Line 96: − + − + − + − + − +
no edit summary
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
== Introduction ==
== Introduction ==
This page helps you to put your [[Sugar on a Stick]] image on a USB flash drive under Linux. If you have questions, trouble or feedback, please let us know on the [[Talk:Sugar on a Stick|SoaS talk]] page. "Sugar on a Stick" is provided in a number of variants. If you can improve these instructions, please edit the page and do so!
This page helps you to put your [[Sugar on a Stick]] image on a USB flash drive under Linux. If you have questions, trouble, or feedback, please let us know on the [[Talk:Sugar on a Stick|SoaS talk]] page. "Sugar on a Stick" is provided in a number of variants. If you can improve these instructions, please edit the page and do so!
== Put [[Sugar on a Stick/Installation/OLPC | SoaS on an OLPC XO-1]] ==
== Put [[Sugar on a Stick/Installation/OLPC | SoaS on an OLPC XO-1]] ==
* 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.
== Full Fedora 11 Install using LVM ==
== Full Fedora 11 Install using LVM ==
Uses [[wikipedia:Logical_Volume_Manager_(Linux)|Logical Volume Manager (LVM)]] layer over the file structure on the USB flash drive.
Uses [[wikipedia:Logical_Volume_Manager_(Linux)|Logical Volume Manager (LVM)]] layer over the file structure on the USB flash drive. Other methods on this page install a LiveUSB image that uses a compressed file system ([[wikipedia:SquashFS|SquashFS]]) to hold the system and content.
THIS IS A WORK IN PROGRESS. Please make suggestions or improvements.
THIS IS A WORK IN PROGRESS. Please make suggestions or improvements.
* Installation of openSUSE.raw file to USB/SD: [[VMware#Image USB/SD Drives]]
* Installation of openSUSE.raw file to USB/SD: [[VMware#Image USB/SD Drives]]
== Put SoaS on to a stick using Fedora and Ubuntu ==
== Put SoaS onto a stick using Fedora and Ubuntu ==
This is known to work in Fedora and Ubuntu.
This is known to work in Fedora and Ubuntu.
::# quit
::# quit
* Also, check to see that you do not already have an existing bootloader (such as GRUB) in the MBR of your stick. (If you have not previously used this stick as a live boot, you can skip this step.) To be sure that the USB stick's MBR is wiped clean, overwrite it completely using:
* Also, check to see that you do not already have an existing boot loader (such as [[wikipedia:GNU GRUB|GRUB]]) in the [[wikipedia:Master boot record|MBR]] of your stick. (If you have not previously used this stick as a live boot, you can skip this step.) To be sure that the USB stick's MBR is wiped clean, overwrite it completely using:
: <tt>dd if=/dev/zero of=/dev/sd''b'' bs=446 count=1</tt>
: <tt>dd if=/dev/zero of=/dev/sd''b'' bs=446 count=1</tt>
:: (Actually, that didn't work for me. But this did:
:: (Actually, that didn't work for me. But this did:
::: <tt>lilo -M /dev/sd''b''</tt>
::: <tt>lilo -M /dev/sd''b''</tt>
:::It put in a standard MBR that boots whichever partition has been called bootable. It does not install LILO as such.)
:::It put in a standard MBR that boots whichever partition has been called bootable. It does not install [[wikipedia:LILO (boot loader)|LILO]] as such.)
* Change mode to make the script executable.
* Change mode to make the script executable.
: <tt>chmod +x livecd-iso-to-disk.sh</tt>
: <tt>chmod +x livecd-iso-to-disk.sh</tt>
* 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-strawberry.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 (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:
:* 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>#!/bin/bash</code><br>
:::<code>udevadm info $*</code>
:::<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 seems to ignore them! (and say all is fine on the last line).
===Transcript===
===Transcript===