Difference between revisions of "Sugar on a Stick/Resources"
m (→Install Methods: add install to usb methods) |
|||
Line 1: | Line 1: | ||
− | <noinclude> | + | <noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}{{TOCright}} |
+ | [[Category:Resource]]</noinclude> | ||
+ | ==Project Definition== | ||
+ | Sugar on a Stick is is a project to distribute and deploy the Sugar Learning Platform on inexpensive USB and SD flash storage devices, which people can carry from home to school to library to clubhouse to any computing device and back home again for seamless continuation of their learning Activities and collaborations. | ||
+ | |||
+ | Simultaneously, the project must | ||
+ | # overcome the technical challenges of building and distributing a transportable GNU/Linux operating system—in the sense that each installation must work on multiple and diverse computing platforms to provide the individual with continuous accessibility to their friends and activities, and | ||
+ | # develop the social structures to best deploy this new, on-line, off-line, resumable, collaborative technical capability within and between the communities where learning occurs. | ||
+ | |||
+ | Thus, '''[[wikipedia:Linux distribution|distribution]]''' no longer just means ''get the software onto an end user's computer'', where it can be stably configured for a single hardware environment. The installation must be ready to be picked up and moved to another, wholly different environment. This goal presents many technical challenges that are new, or made more significant by the goal's importance to the project's essence. | ||
+ | |||
+ | Developing the social mechanisms to imagine, plan, and deploy this leap in technology is also at the core of the project. We must take existing community resources, often old and institutionalized, and reconstruct them around the movements of the learners and their collaborators. Just as the human brain grows and develops in a social context, the Sugar Learning Platform aims to offer a constantly accessible, electronic, supplementary companion set of tools for learning, and ultimately, growing our capabilities. | ||
+ | |||
+ | Having persistence of availability of the learner's Activities and collaborations permits repeated and deep exploration of concepts and phenomena, and moves the external system closer to being an adaptable learning appendage. | ||
+ | |||
==Project Planning== | ==Project Planning== | ||
− | * [[../Goals]] | + | * See [[../TODO]] for some project tasks. |
− | * [http://blueprints.edge.launchpad.net/soas Feature blueprints] | + | * See [[../Goals]] for some specific deployment/distribution obstacles. |
+ | * See our [http://blueprints.edge.launchpad.net/soas Feature blueprints] tracking system for feature development. | ||
=== Use Cases=== | === Use Cases=== | ||
− | This is a list of ways we' | + | This is a list of ways we're working to support SoaS installation and their status. '''TODO:''' replace with a flow chart. |
'''Sugar:''' | '''Sugar:''' | ||
− | + | # On a Stick: | |
− | + | ## Mobile booting using USB boot support in BIOS - ''implemented'' | |
− | |||
− | # On a | ||
− | ## Mobile booting using USB | ||
## Mobile booting using ISO helper CDs - ''implemented'' | ## Mobile booting using ISO helper CDs - ''implemented'' | ||
− | ## Mobile emulation - ''unimplemented'' | + | ## Mobile virtualization or emulation - ''unimplemented'' |
## Combination of booting and emulation - ''unimplemented'' | ## Combination of booting and emulation - ''unimplemented'' | ||
− | ##* | + | ##* [[VMware]] (VMware Player and Appliance on one 8-GB bootable stick, or a 4-GB boot stick and a 4-GB stick with the Appliance) works but is complicated. (Waiting for Fedora 11 to allow VMware Player installation; this workaround uses Ubuntu 9.04 boot stick with VMPlayer.) |
+ | # On a fixed hard disk: | ||
+ | ## Local booting with storage - ''implemented'' via various distros. | ||
+ | ## Local booting with external storage - ''unimplemented'', students would insert their SoaS stick and the fixed system would operate off their transportable data, and optionally, update their stick's software to the latest image. | ||
− | === | + | === Installation Methods === |
# Windows/Mac/Linux | # Windows/Mac/Linux | ||
## LiveUSB creator script - ''implemented'' | ## LiveUSB creator script - ''implemented'' | ||
# Windows | # Windows | ||
− | ## [http://git.sugarlabs.org/projects/soas-emu SoaS-emu] - installer for a | + | ## [http://git.sugarlabs.org/projects/soas-emu SoaS-emu] - installer for a SoaS appliance on the local machine - ''work in progress'' |
## MokaFive portable player installer - ''investigating'' | ## MokaFive portable player installer - ''investigating'' | ||
− | # Other | + | # Virtualization environments |
− | ## | + | ## Boot a SoaS image on a USB device in VirtualBox. See this [http://www.mail-archive.com/soas@lists.sugarlabs.org/msg00259.html discussion thread]. |
+ | ## Live CD which boots a Mac OS X version of VirtualBox and uses a SoaS USB device as the guest OS. See this [http://www.mail-archive.com/soas@lists.sugarlabs.org/msg00312.html discussion thread]. | ||
+ | ## Live CD which boots to live user and autostarts VMware Player (installed in CD SquashFS). Then students can sequentially insert their USB Stick and work on same PC - "idea" [satellit 07/05/2009] | ||
+ | # Other variations | ||
+ | ## Live CD which creates USB sticks - ''works in SoaS Strawberry'' | ||
### Insert the target USB storage device into your computer, | ### Insert the target USB storage device into your computer, | ||
### Boot from a CD-ROM burnt with the soas-strawberry.iso image, | ### Boot from a CD-ROM burnt with the soas-strawberry.iso image, | ||
Line 33: | Line 52: | ||
### Install the live image to the USB device by executing the following, <u>single</u> command with arguments:<br><code>/mnt/live/LiveOS/livecd-iso-to-disk --noverify --overlay-size-mb 300 --home-size-mb 160 --unencrypted-home --delete-home /dev/sr0 /dev/sdb1</code> | ### Install the live image to the USB device by executing the following, <u>single</u> command with arguments:<br><code>/mnt/live/LiveOS/livecd-iso-to-disk --noverify --overlay-size-mb 300 --home-size-mb 160 --unencrypted-home --delete-home /dev/sr0 /dev/sdb1</code> | ||
###:'''Note:''' If you have more than 1 hard disc or USB device, you should verify the name of the USB storage device by reviewing the output of the <code>mount</code> command before step 5 above. | ###:'''Note:''' If you have more than 1 hard disc or USB device, you should verify the name of the USB storage device by reviewing the output of the <code>mount</code> command before step 5 above. | ||
− | ## zyx-liveinstaller (in | + | ## zyx-liveinstaller (in Terminal) in SoaS v2 betas can be used to make USB installations from the running live CD. - "works in latest iso" |
− | ## dd install to | + | ## dd install to USB device with F12 dual mode .iso "works, but offers no persistence" |
− | |||
− | |||
=== More Information === | === More Information === | ||
* [http://git.sugarlabs.org/projects/soas SoaS Gitorious home] - Tools to build Sugar on a Stick images. | * [http://git.sugarlabs.org/projects/soas SoaS Gitorious home] - Tools to build Sugar on a Stick images. | ||
Line 42: | Line 59: | ||
* For a testing drawing space, check [[olpc:User_talk:FGrose/sandbox/SoaS| this]]. | * For a testing drawing space, check [[olpc:User_talk:FGrose/sandbox/SoaS| this]]. | ||
− | == Home View Design== | + | === Home View Design === |
− | See [[ | + | See [[Design Team/Proposals/Home View|this page]] for ideas about the Home view design. |
=== Initial Home View Activities === | === Initial Home View Activities === | ||
Discussion of which Activities should be visible on initial display of the Home view is appropriate here. | Discussion of which Activities should be visible on initial display of the Home view is appropriate here. | ||
See this [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03685.html sugar-devel thread] for the background. | See this [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03685.html sugar-devel thread] for the background. | ||
− | |||
− |
Revision as of 17:44, 1 November 2009
Project Home · Get Involved · Contacts · Resources · FAQ · Roadmap · To Do · Meetings
Project Definition
Sugar on a Stick is is a project to distribute and deploy the Sugar Learning Platform on inexpensive USB and SD flash storage devices, which people can carry from home to school to library to clubhouse to any computing device and back home again for seamless continuation of their learning Activities and collaborations.
Simultaneously, the project must
- overcome the technical challenges of building and distributing a transportable GNU/Linux operating system—in the sense that each installation must work on multiple and diverse computing platforms to provide the individual with continuous accessibility to their friends and activities, and
- develop the social structures to best deploy this new, on-line, off-line, resumable, collaborative technical capability within and between the communities where learning occurs.
Thus, distribution no longer just means get the software onto an end user's computer, where it can be stably configured for a single hardware environment. The installation must be ready to be picked up and moved to another, wholly different environment. This goal presents many technical challenges that are new, or made more significant by the goal's importance to the project's essence.
Developing the social mechanisms to imagine, plan, and deploy this leap in technology is also at the core of the project. We must take existing community resources, often old and institutionalized, and reconstruct them around the movements of the learners and their collaborators. Just as the human brain grows and develops in a social context, the Sugar Learning Platform aims to offer a constantly accessible, electronic, supplementary companion set of tools for learning, and ultimately, growing our capabilities.
Having persistence of availability of the learner's Activities and collaborations permits repeated and deep exploration of concepts and phenomena, and moves the external system closer to being an adaptable learning appendage.
Project Planning
- See Sugar on a Stick/TODO for some project tasks.
- See Sugar on a Stick/Goals for some specific deployment/distribution obstacles.
- See our Feature blueprints tracking system for feature development.
Use Cases
This is a list of ways we're working to support SoaS installation and their status. TODO: replace with a flow chart.
Sugar:
- On a Stick:
- Mobile booting using USB boot support in BIOS - implemented
- Mobile booting using ISO helper CDs - implemented
- Mobile virtualization or emulation - unimplemented
- Combination of booting and emulation - unimplemented
- VMware (VMware Player and Appliance on one 8-GB bootable stick, or a 4-GB boot stick and a 4-GB stick with the Appliance) works but is complicated. (Waiting for Fedora 11 to allow VMware Player installation; this workaround uses Ubuntu 9.04 boot stick with VMPlayer.)
- On a fixed hard disk:
- Local booting with storage - implemented via various distros.
- Local booting with external storage - unimplemented, students would insert their SoaS stick and the fixed system would operate off their transportable data, and optionally, update their stick's software to the latest image.
Installation Methods
- Windows/Mac/Linux
- LiveUSB creator script - implemented
- Windows
- SoaS-emu - installer for a SoaS appliance on the local machine - work in progress
- MokaFive portable player installer - investigating
- Virtualization environments
- Boot a SoaS image on a USB device in VirtualBox. See this discussion thread.
- Live CD which boots a Mac OS X version of VirtualBox and uses a SoaS USB device as the guest OS. See this discussion thread.
- Live CD which boots to live user and autostarts VMware Player (installed in CD SquashFS). Then students can sequentially insert their USB Stick and work on same PC - "idea" [satellit 07/05/2009]
- Other variations
- Live CD which creates USB sticks - works in SoaS Strawberry
- Insert the target USB storage device into your computer,
- Boot from a CD-ROM burnt with the soas-strawberry.iso image,
- Launch Terminal,
- Switch to the root user,
su -l
- Unmount the USB device,
umount /dev/sdb1
- Install the live image to the USB device by executing the following, single command with arguments:
/mnt/live/LiveOS/livecd-iso-to-disk --noverify --overlay-size-mb 300 --home-size-mb 160 --unencrypted-home --delete-home /dev/sr0 /dev/sdb1
- Note: If you have more than 1 hard disc or USB device, you should verify the name of the USB storage device by reviewing the output of the
mount
command before step 5 above.
- Note: If you have more than 1 hard disc or USB device, you should verify the name of the USB storage device by reviewing the output of the
- zyx-liveinstaller (in Terminal) in SoaS v2 betas can be used to make USB installations from the running live CD. - "works in latest iso"
- dd install to USB device with F12 dual mode .iso "works, but offers no persistence"
- Live CD which creates USB sticks - works in SoaS Strawberry
More Information
- SoaS Gitorious home - Tools to build Sugar on a Stick images.
- SoaS Desktop Manager Sugar_on_a_Stick/sdm
- For a testing drawing space, check this.
Home View Design
See this page for ideas about the Home view design.
Initial Home View Activities
Discussion of which Activities should be visible on initial display of the Home view is appropriate here. See this sugar-devel thread for the background.