From Teaching Open Source
< RIT
< RIT
|
- Purpose
- Learn about Sugar on a Stick,
- Discover something about Live USB technology and virtualization,
- Propose solutions to any problems discovered and improvements to this laboratory exercise, documenting them in the wiki.
- Problem questions
- Will Sugar on a Stick boot successfully on your personal laptop or workstation? What about the classroom workstations?
- Can Sugar-style collaboration occur with Sugar on a Stick in these environments? With XOs as well?
- What additional features are available in Sugar on a Stick? How might they be useful to your projects?
- What capabilities does a virtual machine provide? How might they be useful to your projects?
- Collectively, report your investigation in a standard laboratory report format at this page. Organize your reporting as the page history will be used to evaluate your work.
- Answer the #Problems section questions on your User:Learner/Assignment pages.
- Report & Problems Due
- Tuesday noon 13 October 2009
[edit] References
[edit] SoaS images
- A 1-GiB or larger capacity USB flash storage device is required.
- Follow instructions at http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Strawberry for your operating system.
- There will be some copies of the image and program files available on USB devices and CD ROMs. (Having copies available before class will save time.)
- Load Sugar on a Stick Strawberry onto your USB device.
- Boot your personal laptop and classroom workstation.
- Install VirtualBox on your personal laptop or workstation and install and run a SoaS virtual machine [1]. (Pre-installing VirtualBox for your environment ahead of class is advised.)
- Visit http://activities.sugarlabs.org and download and install updates to Browse and Physics to your USB device or virtual machine.
[edit] Problems
(Answers to problem questions in this section are due at the laboratory report due date and time. They are to be individually completed on a User:Learner/Assignment page.)
- Identify the SoaS bugs recorded at the following sites:
- If you have any significant comments or observations to add to any of these bug reports or a new bug to report, do so and link your comments to your report.
- See these references for bug reporting, triage guide,
- Note: Duplicate reports will have negative consequences, while identifying duplicates and triaging have positive consequences.