Talk:Sugar on a Stick/Installation/Variations: Difference between revisions

Satellit (talk | contribs)
Soas stick that writes new live USB's
Satellit (talk | contribs)
 
(8 intermediate revisions by 2 users not shown)
Line 46: Line 46:
  soas-v2-Blueberry          /home/liveuser/Activities
  soas-v2-Blueberry          /home/liveuser/Activities
  soas-i386-Nightly composes: /usr/share/sugar/activities
  soas-i386-Nightly composes: /usr/share/sugar/activities
soas-v3-Mirabelle:          /usr/share/sugar/activities
  F12-EDU-spin:              /home/xxxx/Activities
  F12-EDU-spin:              /home/xxxx/Activities


Line 118: Line 119:


'''Alternate Download Locations:'''
'''Alternate Download Locations:'''
  http://people.sugarlabs.org/Tgillard/libsugarize.so
  http://people.sugarlabs.org/Tgillard/sugarize/libsugarize.so
  http://people.sugarlabs.org/Tgillard/sug.txt (rename without .txt after download)
  http://people.sugarlabs.org/Tgillard/sugarize/sug.txt(rename without .txt after download)
http://people.sugarlabs.org/Tgillard/sugarize/plain.svg
http://people.sugarlabs.org/Tgillard/sugarize/l.svg
http://people.sugarlabs.org/Tgillard/sugarize/ff.svg
 


References and Download Mirrors:
References and Download Mirrors:
Line 158: Line 163:
*makes a USB with 0.84.2 sugar
*makes a USB with 0.84.2 sugar


   
===How to install to a 4GB USB using liveinst(ANACONDA) from SoaS===
====CASE 1 Using a burned Soas Live CD====
* '''Using Preformatted 4 GB USB Target:'''
4GB USB pre-formatted using gparted outside of soas:
 
  /boot ext4 196
/ ext4 3570
 
=====Step by Step Procedure=====
'''NOTE THIS IS A VERY DANGEROUS PROCEDURE AS YOU CAN DESTROY YOUR COMPUTER'S HARD DRIVE'''
 
'''(NOT FOR NOVICES: FOLLOW THIS PROCEDURE EXACTLY)'''
 
*Boot Soas USB:
*sugar-terminal:
  su
  liveinst
(Graphical Installer starts)
*next
*Basic Storage Devices
  "Please select the drives you'd like to install the operating system on, as well as any drives you'd like to automatically mount to your system, below::
  ( ) Hard Disk (netbook) /dev/sda  DO NOT SELECT
  (+) Lexar JD Firefly (Target for Install)  SELECT THIS ONE 
*next
  "finding storage devices"
  Host Name_______(localhost)
  *next
  Select City (time zone)
*next
  Root Password
  ___________
  Confirm
  ___________
*next
*Create Custom Layout
NOTE: /dev/sda is most likely your Hard Disk '''Do NOTHING with it'''
unless you want to install to Hard Disk and Delete '''ALL''' of it's Contents.
*Please Select a Device (look at label at top of page to choose correct USB)
labeled on top of screen:(Lexar JD Firefly)
*next
^Hard Drives
  sdb                  (TargetUSB)
    sdb1      199    ext4     
    sdb2    3624    ext4
   
Editing instructions:
click on
*sdb1
*edit
  Mount Point:/boot
*OK
click on
*sdb2
*edit
  Mount Point/
* OK
*next
*Write changes to disk
  creates filesystems...
*Boot loader operating system list
(x) "Install boot loader on /dev/sdb"
  Boot Loader operating system list
  (x) Fedora /dev/sdb2
*next
(Installation Begins)
"Copying Live image to Hard Drive"
"Performing post-installation filesystem changes"
"Bootloader"
"Congratulations, your Fedora installation is complete
*Close
(shut down installer Soas live CD)
remove Soas live CD
 
====CASE 2 In a Booted Fedora-13-i686-Live-SoaS.iso, script written, 4GB USB====
 
script
./livecd-iso-to-disk  --format --reset-mbr --overlay-size-mb 1200 /home/xxxx/Desktop/Fedora-13-i686-Live-SoaS.iso /dev/sdg*
ACER ASPIRE ONE AO532h V1.05
Laptop Hard Drive=/dev/sda
 
* '''Using Preformatted 4 GB USB Target:'''
 
4GB USB pre-formatted using gparted outside of soas:
 
/boot ext4 196
/ ext4 3570
 
=====Step by Step Procedure=====
'''NOTE THIS IS A VERY DANGEROUS PROCEDURE AS YOU CAN DESTROY YOUR COMPUTER'S HARD DRIVE'''
 
'''(NOT FOR NOVICES: FOLLOW THIS PROCEDURE EXACTLY)'''
 
*Boot Soas USB:
*sugar-terminal:
su
liveinst
(Graphical Installer starts)
*next
keyboard select
 
*Basic Storage Devices
"Please select the drives you'd like to install the operating system on, as well as any drives you'd like to automatically mount to your system, below::
( ) Hard Disk (netbook) /dev/sda  DO NOT SELECT
(+) Lexar JD Firefly (Live Soas USB Booted from)PRESELECTED
(+) SanDisk Cruzer  (Target for Install)  SELECT THIS ONE
*next
"finding storage devices"
Host Name_______
*next
Select City (time zone)
*next
Root Account
  ___________
  ___________
 
*next
*Create Custom Layout
NOTE: /dev/sda is most likely your Hard Disk '''Do NOTHING with it'''
unless you want to install to Hard Disk and Delete '''ALL''' of it's Contents.
 
(select from Table by using arrows to '''move both USB's to the right''')
*next
sd(b) (boot USB) Lexar JD Firefly
sd(c) (TargetUSB) SanDisk Cruzer
 
*Please Select a Device (look at label at top of page to choose correct USB)
labeled on top of screen:(SandDisk Cruzer)
*sdc1
*edit
Label:/boot
*OK
*sdc2
*edit
Label:/
*OK
*next
*Write changes to disk
  creates filesystems...
*Boot loader operating system list
( ) "Install boot loader on /dev/sdb" [Change device] '''select this box'''
 
change selection to
 
"first sector of of boot partition" /dev/sdc1
"Bios Drive Order:"
(reverse order)
first  bios drive = sdc Sandisk
second bios drive = sdb Firefly
OK
*info window:
  Boot loader on /dev/sdc1
  Default Device Fedora /dev/sdc2
*next
(Installation Begins)
"Copying Live image to Hard Drive"
"Performing post-installation filesystem changes"
"Bootloader"
"Congratulations, your Fedora installation is complete
*Close
(shut down installer Soas live CD)
remove Soas live USB
 
===='''USE new USB for the first time'''====
Boot from your newly installed Target USB:
 
light brown SUGAR splash screen
Plymouth animation circle
Firstboot
license
Create USER
  name___________
  password___________#
Date and Time
send profile (smolt)
Plymouth
Blue gdm login screen
login with your password#
SUGAR starts....
 
===From https://bugzilla.redhat.com/show_bug.cgi?id=460854===
===From https://bugzilla.redhat.com/show_bug.cgi?id=460854===


--- Comment #4 from Jeremy Katz <katzj@redhat.com> 2009-02-04 09:15:40 EDT --- The problem is that the overlay fills up and that there is then nothing that can really be done. Fedora 10 adds the 'reset_overlay' option that you can pass on the kernel command line which helps to recover, but ultimately, we need something better than dm-snapshot to use for the overlay
--- Comment #4 from Jeremy Katz <katzj@redhat.com> 2009-02-04 09:15:40 EDT --- The problem is that the overlay fills up and that there is then nothing that can really be done. Fedora 10 adds the 'reset_overlay' option that you can pass on the kernel command line which helps to recover, but ultimately, we need something better than dm-snapshot to use for the overlay
Return to "Sugar on a Stick/Installation/Variations" page.