174
edits
Changes
Jump to navigation
Jump to search
Line 32:
Line 32: − + Line 44:
Line 44: − + − + Line 51:
Line 51: − + − + − + − + − + − + − + − +
→Linux instructions: formatting tweaks
* Then check to see that the partition is marked as bootable,<br>
* Then check to see that the partition is marked as bootable,<br>
: <tt>sudo fdisk '''-l'''</tt> ''<----that's a lowercase letter L for the List option.''
: <tt>sudo fdisk '''-l'''</tt> ''<----that's a lowercase letter 'L' for the '''l'''ist option.''
You should see output that looks like this:
You should see output that looks like this:
Disk /dev/sdb: 1047 MB, 1047265280 bytes
Disk /dev/sdb: 1047 MB, 1047265280 bytes
: If not, then
: If not, then
:* For Ubuntu 8.10, menu: System -> Administration -> Partition Editor (GParted).
:* For Ubuntu 8.10, menu: System -> Administration -> Partition Editor (GParted).
::# Select your USB device (/dev/sdb in your case),
::# Select your USB device (/dev/sd''b'' for the rest of these instructions),
::# then your partition (/dev/sdb1),
::# then your partition (/dev/sd''b1''),
::# then menu: Partition -> Manage Flags,
::# then menu: Partition -> Manage Flags,
::# check the boot box,
::# check the boot box,
:* For Fedora,
:* For Fedora,
::# <tt>parted /dev/sdb</tt>
::# <tt>parted /dev/sd''b''</tt>
::# toggle 1 boot
::# toggle 1 boot
::# 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 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:
: <tt>dd if=/dev/zero of=/dev/sdb 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/sdb</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 LILO as such.)
* Unmount the drive,<br>
* Unmount the drive,<br>
: <tt>sudo umount /dev/sdb1</tt>
: <tt>sudo umount /dev/sd''b1''</tt>
* 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/sdb1</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).
== Alternative installation methods ==
== Alternative installation methods ==