Difference between revisions of "Sugar on a Stick/ZyX-LiveInstaller"

From Sugar Labs
Jump to navigation Jump to search
(→‎ZyX-LiveInstaller: cleanups, note I did just do a real no /boot test, and for me, it works)
Line 4: Line 4:
 
* note: this is *not* a method to create a SugarOnAStick (LiveUSB).  Though you can install to an external usb drive/stick, resulting in an installation that very similarly boots your system to the Sugar UI.  The difference is that the resulting system is not a 'Live' system.  This means that it uses a normal filesystem, instead of a compressed read-only filesystem with a read-write snapshot/overlay above, as a 'LiveUSB' does.  
 
* note: this is *not* a method to create a SugarOnAStick (LiveUSB).  Though you can install to an external usb drive/stick, resulting in an installation that very similarly boots your system to the Sugar UI.  The difference is that the resulting system is not a 'Live' system.  This means that it uses a normal filesystem, instead of a compressed read-only filesystem with a read-write snapshot/overlay above, as a 'LiveUSB' does.  
  
* IMPORTANT WARNING: understand that this is a fairly new piece of open source software, that will overwrite entire partitions or disks ** as well as your bootloader ** during installation.  In this release of SoaS, it is intended only for users that are familiar with the risks and possible complications of installing a Linux distribution to system disk.
+
* IMPORTANT WARNING: understand that this is a fairly new piece of open source software, that will overwrite entire partitions or disks ** as well as your bootloader ** during installation.  In this release of SoaS, it is intended only for users that are familiar with the risks and possible complications of installing a Linux distribution to system disk.  If you need a dual boot configuration, you will need to configure grub yourself (at least for the current version).
  
 
* To use
 
* To use
Line 15: Line 15:
 
::* note: formatting in the partitioner is not required.
 
::* note: formatting in the partitioner is not required.
 
::* exit the partitioner by hitting the X in the top corner of window.
 
::* exit the partitioner by hitting the X in the top corner of window.
:* read and follow the simple wizard, choosing destination volumes/partitions for boot, root, and swap.  ( swap is optional).
+
:* read and follow the simple wizard, choosing destination volumes/partitions for root, boot, and swap.
 
* This is a *destructive* install, meaning that the contents of the disks or partitions you choose will be overwritten entirely.
 
* This is a *destructive* install, meaning that the contents of the disks or partitions you choose will be overwritten entirely.
 
* During installation, you are free to use other activities.
 
* During installation, you are free to use other activities.
 
* After installation completes, you may remove the LiveUSB or LiveCD, and continue using the newly installed system - ''without rebooting''!!!.  This means that anything done with the system before, during, or after installation persists into the installed system.
 
* After installation completes, you may remove the LiveUSB or LiveCD, and continue using the newly installed system - ''without rebooting''!!!.  This means that anything done with the system before, during, or after installation persists into the installed system.
 
* For more information, see the upstream project website [http://filteredperception.org/smiley/projects/zyx-liveinstaller]
 
* For more information, see the upstream project website [http://filteredperception.org/smiley/projects/zyx-liveinstaller]

Revision as of 01:15, 9 December 2009

ZyX-LiveInstaller

  • ZyX-LiveInstaller allows you to install SoaS when it is already running from either a LiveUSB device or LiveCD media to a system or external disk. This results in what is considered a traditional operating system installation on disk (or USB-Stick/SD-Card).
  • note: this is *not* a method to create a SugarOnAStick (LiveUSB). Though you can install to an external usb drive/stick, resulting in an installation that very similarly boots your system to the Sugar UI. The difference is that the resulting system is not a 'Live' system. This means that it uses a normal filesystem, instead of a compressed read-only filesystem with a read-write snapshot/overlay above, as a 'LiveUSB' does.
  • IMPORTANT WARNING: understand that this is a fairly new piece of open source software, that will overwrite entire partitions or disks ** as well as your bootloader ** during installation. In this release of SoaS, it is intended only for users that are familiar with the risks and possible complications of installing a Linux distribution to system disk. If you need a dual boot configuration, you will need to configure grub yourself (at least for the current version).
  • To use
  • boot your SugarOnAStick
  • start the terminal activity, type in lowercase 'zyx-liveinstaller', then press enter.
  • start the partitioner 'gparted' if necessary
  • you will need at least a single partition for the root filesystem, that is greater than 2GB. Some disks labeled and sold as 2GB may not be quite large enough.
  • optionally create a seperate partition for the /boot filesystem, at least 42MB in size
  • optionally create a seperate partition for swap space, typically 1 or 2 times the size of ram in your system. This will allow the use of hibernation (suspend-to-disk, via pm-hibernate command run from root terminal shell).
  • note: formatting in the partitioner is not required.
  • exit the partitioner by hitting the X in the top corner of window.
  • read and follow the simple wizard, choosing destination volumes/partitions for root, boot, and swap.
  • This is a *destructive* install, meaning that the contents of the disks or partitions you choose will be overwritten entirely.
  • During installation, you are free to use other activities.
  • After installation completes, you may remove the LiveUSB or LiveCD, and continue using the newly installed system - without rebooting!!!. This means that anything done with the system before, during, or after installation persists into the installed system.
  • For more information, see the upstream project website [1]