Sugar Labs - User contributions [en]

Wish list

2014-08-19T02:14:55Z

David Kergyl: /* Sugar wish list */ GNOME default installer "app" script

<noinclude>[[Category:Wish list]]</noinclude>

This is a page composed of selected [[:Category:Wish list | wish list pages]] on the Sugar Labs wiki.

Visit [[:Category:Wish list]] for the known lists.

Please click a section heading below to visit a featured wish list, and then add your wish.

==[[Teacher feedback]]==
{{:Teacher feedback}}
 

==[[Sugar/Wish list|Sugar wish list]]==
{{:Sugar/Wish list}}
 
=== '''Create a Sugar installation script that users can find with the default GNOME software installer''' ===

>"Fedora 20's default GNOME3 graphical software installer tool fails to find Sugar, reportedly as Sugar is not considered to be an 'application'."

This is a significant problem. Sugar will be more successful if Linux users can easily find it by a simple keyword search in the default installer. A user should not have to install a new installation app (yumex) in order to find Sugar. I suggest that the team create an "application" that (i) meets Fedora's criteria for applications and (ii) automatically executes a script that downloads and installs the necessary components of Sugar. Better yet, the Sugar Learning Platform Package App could even give a user a set of choices of available components and/or activity packages to add to the script.

==[[Activity Library/Wish list|Activity Library wish list]]==
{{:Activity Library/Wish list}}
 

==[[Features/GTK3/API wish list]]==
{{:Features/GTK3/API_wish_list}}
 

==[[School Server Wish List]]==

==See also==
* [[Request New Features]]

Talk:Fedora

2014-08-19T02:08:10Z

David Kergyl: /* GNOME3 default software installer fails to find Sugar */ new section

==Split page==
Please consider reorganizing this page to start with the current stable release of Fedora and the easiest way to run Sugar with it. Follow that by sections for alpha/beta versions of Fedora Sugar, a short section with links to SoaS, and then links to subpages for ARM, PPC, & older versions of Fedora Sugar. Guidance for GNOME on Fedora and other peripheral content should also probably be on subpages. --[[User:FGrose|FGrose]] 11:45, 30 June 2012 (EDT)
:Pages split --[[User:Satellit|Satellit]] 20:49, 12 December 2012 (EST)
::Having now created pages for Fedora 18, 19, and 20, entry level Sugar information (however up to date) remains, but mixed in with [legacy] Fedora 17. I propose moving all Sugar material, (which I would like to expand) above Fedora 17 material on this page. I wonder whether later, a new page for Fedora 17, would fit better with the current Fedora page naming? Any better suggestions? --[[User:Inkyfingers|Inkyfingers]] ([[User talk:Inkyfingers|talk]]) 17:59, 12 October 2013 (EDT)
::: I would like this page to be the primary location for information on using '''Sugar''' on the current stable release of Fedora (as suggested in the first sentence above), and so, would have to be edited to remain current. The Fedora NN pages should address any special version-specific information or testing, advice, etc., and be considered as secondary pages, which naturally become dated with time. So, yes I agree that the Fedora 17 content could be moved to a Fedora 17 page, and this page always updated for the easiest way to run Sugar on the current version of Fedora. Information not related to running Sugar on Fedora should be minimal on this page. --[[User:FGrose|FGrose]] ([[User talk:FGrose|talk]]) 19:41, 12 October 2013 (EDT)
===Content needing organizing ===
====Multiple Machine Caching with yum====
*http://yum.baseurl.org/wiki/YumMultipleMachineCaching
:store rpms in a cache for installation to multiple Computers
====Keyring Password Explained====
what do you have to enter when connecting to wlan, the keyring password or the wlan-password?
first i must enter the keyring password (root password here) and then i entered the wireless password
the keyring-password should not be your root password, it should be your users password so automatically unlocking could work
it may happen but during current session, after i reboot it appears again
ok, it is the keyring issue, assuming your distro has configured keyring correctly, changing the password should work
root pass?
change the keyring password to your users password
in settings ?
in seahorse
system settings?
as user (the login-keyring)
keyring is a way to store your "gnome" passwords
So, with one password (the keyring one), you "auto-type" the passwords it contains
if the keyring-password is your login password, it's automatically authenticated
keyring stores the passwords encrypted with the according keyring-password, and automatic unlocking works by getting the password through pam on login through gdm and then use it to unencrypt the passwords - and that can only work if your login-password is the same as the keyring-password

why doesn't gnome 3 display "interactive dialogs" when applications ask for input
yes, also from gnome 3
when you run the shell script from nautilus, it doesn't display a dialog
"Enter passphrase for ..."
you can use zenity for that
try moving /usr/share/gdm/autostart/LoginWindow/gnome-session-check-accelerated.desktop somewhere else
didn't know you needed anything additional for that.. was it always like that or did gnome 2 have that by default?
maybe thats the seahorse/keyring integration, that stuff has changed quite a bit in 3.0
but i thought you meant a more generic approach of showing dialogs from scripts
i'm actually doing the ssh-add from a process spawned by a pygtk app
if it is only this specific case, you should probably still use keyring/seahorse (whatever should do that now) as it would not be passing around passwords unencrypted between processes (at least afaik)
worked!
do you somehow run gdm with a different driver or some weird setup like that?
so it's not possible to get the old behavior, and it needs some additional code to get it to work with seahorse/keyring?
which distro is this?
fedora 15 beta
i've tested the same code on fedora 14 and linuxmint (both gnome 2)
when the ssh-add {key_path} process is spawned, the GUI dialog appears asking you to type in your passphrase
ssh-add succeeds, and them the rest of the pygtk app continues
it doesn't even care whether the key is password protected or anything
i think there needs a daemon to be running that doesn't get started by fedora
this happens both in standard and fallback mode
try launching seahorse-daemon

====AutoStart====
ln -s /usr/share/applications/xxxx.desktop ~/.config/autostart/
don't remember if I had to manually add it to the startup apps (run
gnome-session-properties) or using a preference in xxxx itself, but I
have it running on login on my laptop. The icon shows up in the
notification tray - mouse to the lower right corner to bring it up -
this is where all legacy tray icons will show up.

====fix screensize in sugar-emulator====
terminal:
su -
(password)
gedit /usr/share/applications/sugar-emulator.desktop
edit line 6: Exec='''sugar-emulator -f'''
(see [[Emulator/Full Screen|how to configure full screen]])
save
Logout
login

====show desktop as icon in favorites====
add programs install "alacarte"
open alacarte
make new
application
command "nautilus Desktop"
save
Run from applications
Make favorite

====key shortcuts====
* System (Windows) key: Switch between overview and desktop
* Alt+F1: Switch between overview and desktop
* Alt+F2: Pop up command dialog
* Alt+Tab: Pop up window cycler
* Alt+Shift+Tab: Cycle in reverse direction in the window cycler
* Alt+`: Switch between windows of the same application in Alt+Tab
* Ctrl+Alt+Tab: Pop up place cycler
* Ctrl+Shift+Alt+R: Start and end screencast recording
* Ctrl+Alt+D: Show desktop and raise windows back
* Ctrl+Alt+Up/Down arrow: Switch between workspaces
* Ctrl+Alt+Shift+Up/Down arrow: Move the current window to a different workspace
Most keybindings can be viewed under the User Menu -> System Settings -> Keyboard -> Shortcuts

==== List of Autostart programs when starting gnome-shell====
ALT F2 gnome-session-properties

====='''move intro screens that are too large for 800x600'''=====
; alt+f7 and then the arrow keys
; alt+f8 Resize
; shift and arrow keys
:https://bugzilla.gnome.org/show_bug.cgi?id=262546
It's worth nothing, for Metacity >= 2.13.2, that if the window doesn't have a
minimum size hint larger than the screen then Metacity will now force such
windows to be onscreen (by shrinking and moving them as necessary). If the
window has a minimum size hint larger than the screen, then the user can use
'''alt+left-click-and-drag (or alt+f7 and then the arrow keys) to move the window
upwards''' (including moving the titlebar offscreen) in order to get to the
forward button. Yeah, that's just a workaround for windows that are too large,
but it may be helpful information for those waiting for the UI changes to make
the window usable on 800x600 resolutions. :)
clip....
why not use a keyboard shortcut. the "next" button is marked "forward" so i hit '''alt + f''' and guess
what, i was able to successfully install the program.

====Reload shell ALT+F2 r (reload)====
: use to recover Applications lists if they go missing and after alacarte edits

====http://live.gnome.org/GnomeShell/CheatSheet====
:How to show user pictures on the GDM LOGIN screen
::Click "my account" on the top panel lets me edit the picture, and
::adding a picture will show it on the GDM login screen.

If you hold down Alt, a 'Shut Down' option appears in place of suspend.

====Alt+Tab switches between windows====
: hot corner = upper left switches between shell and running applications
: '''Alt+F2 allows entering a command to launch an application.'''
the Shell simply always behaves so there's exactly one empty workspace.
So when you start a session you have one workspace.
As soon as you run something it goes into that workspace and
you get a second empty workspace. As soon as you put any app into that
empty workspace, a new empty workspace is created. If you remove
everything from any workspace, it will disappear, so there's still only
one empty workspace at the bottom of the list. So, there's never any
need to manually add a new workspace. Pretty neat system.

====GNOME 3 is not expected to work in virtualized environments====
I've just installed F15 alpha in a virtualbox machine and at the first boot I
get a gnome 3 error explaining that it can't be fully initialised because 3D is
not supported.
GNOME3 is not expected to work in virtualized environments where
hardware accelerated graphics are not available.

From http://gnome3.org/faq.html ...
The GNOME 3 desktop does require hardware accelerated graphics
in order to provide a cutting-edge experience however, and the
complete GNOME 3 experience will only be available on computers
capable of this. Do not worry though: GNOME 3 will come complete
with a fallback interface which will provide an excellent
experience in the absence of hardware acceleration, and which
incorporates many of the improvements that can be found in GNOME
3.
-------------------------------------------
test Digest, Vol 85, Issue 60, Message: 7
It's kind of a definition issue. GNOME *Shell* requires acceleration.
But technically GNOME 3 does not; the fallback interface is still
considered to be 'GNOME 3'. So you do need acceleration to get the Shell
interface that's the 'big new thing' in GNOME 3, but still, if you don't
have acceleration and you get the fallback interface instead, what
you're running is still GNOME 3. Just GNOME 3's fallback interface.
Adam Williamson
Message: 8
In any case, VBox with 3d accelleration enables and 128MB for video memory
is not sufficient for GShell. (VBox 4.0.4)
Message: 13
Also, on that last note, we should clarify that right now Shell doesn't
work even in virtualized environments where accelerated graphics *are*
available, e.g. VirtualBox with appropriate hardware and drivers. In
theory it should be possible to make this work, but in practice it
currently doesn't.
So there's two angles we can approach this from; make Shell run with
software GL, or fix up Shell to work with virtualized graphics
acceleration passthrough. But it's not at all guaranteed that we'll
manage either in time for f15.

The minimum memory required is 1GB, due to anaconda changes.
When you see "populate_rootfs" in the panic, it's caused by that.

====[http://sunglint.wordpress.com/2011/10/26/fedora-16-vs-macbook-pro-or-air/ Fedora-16-vs-macbook-pro-or-air]====
:click this link ^
:Add features to Anaconda to aid installation on Apple computers https://bugzilla.redhat.com/show_bug.cgi?id=503149

==== MacPro and f15 Boot====
*Clips from #fedora-qa 04/04/2011 MacPro and f15 Boot
I have a macbook pro and have run fedora 14 on it with great success. 15 alpha, on the other hand, is not going well. The installation comes saying something about "installing *** on EFI ***"
which i just dismiss/ignore, but when i try to boot after installation has completed, it wont. Just saying something like "no file found". Should i do something
special to install 15 alpha on a EFI system?
Yeah... you may have to run gptsync (I think that's what it's called)
no, you don't need to install again, but you will need to gain access to the installed partitions from another system (whether it's a Fedora live image)
referring to the gptsync that is provided be rEFIt
I formatted the partition to make space for a working distro. i have refit installed and my mbp boots to that at startup by default. that didnt make 15 alpha work. 14 did though
you may need to enter the boot partition tool from the rEFIt menu and when it asks to run gptsync, say yes
okay. I will try to install again later and do that. Thank you so far. Will get back to you guys
I belive anytime partitioning changes occur on a macbook, you do need to run gptsync. Since the EFI implementation by apple isn't fully compliant with the standard, extra steps are required
you don't need to reinstall ... just run gptsync from the rEFIt menu
just need to get your partitions synced up

== GNOME3 default software installer fails to find Sugar ==

>"Fedora 20's default GNOME3 graphical software installer tool fails to find Sugar, reportedly as Sugar is not considered to be an 'application'."

This is a significant problem. Sugar will be more successful if Linux users can easily find it by a simple keyword search in the default installer. A user should not have to install a new installation app in order to find Sugar. I suggest that the team create an "application" that (i) meets Fedora's criteria for applications and (ii) automatically executes a script that downloads and installs the necessary components of Sugar. Better yet, the Sugar Learning Platform Package App could even give a user a set of choices of available components and/or activity packages to add to the script.

Talk:USpeak

2013-12-10T18:08:35Z

David Kergyl: Add comment re Google service.

Good, thorough proposal. It answers all my questions.

[[User:Homunq|Homunq]] 00:43, 31 March 2009 (UTC)

* Could this now be implemented through the Google voice-recognition service that is available on Android smartphones?

Talk:Downloads

2013-12-10T17:54:51Z

David Kergyl: /* Download Questions */ Suggest warming re LiveUSB method re overlay corruption / short-term-use only.

<noinclude>
</noinclude>
==A review of installation methods==

:''(This is a work in progress. Please review and contribute.)''

There are many alternative methods to install Sugar. The options can be very confusing because of the technical details and features that may be unfamiliar.

This page begins to itemize some of the many options that are available for those interested in learning more about the possibilities.

'''Note:''' When dealing with flash memory storage devices, such as 'USB sticks' and 'SD cards', one should be advised that changing the device format may affect its service lifetime. Fortunately, the manufacturer's default format is suitable for many of the common options.
 The methods that require reformatting are indicated by a colored background such as this. 
{{Iframe|collapsed=|See this discussion, [[olpc:How to Damage a FLASH Storage Device |How to Damage a Flash Storage Device]] |http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device|900|200|1}}

==Bootable CD of Trisquel 4.5 for MacBook Air==
:Download http://devel2.trisquel.info/slaine/iso/trisquel_4.5-20110203_amd64.iso
:Use External USB DVD/CD Drive hold down the "C" key on MacBook Air until booted from CD
::NOTE: hit f4 on boot screen add "xdriver=vesa nomodeset" to end of boot line for correct boot on MacBook Air
::Works nicely. NO Wireless or Magic Mouse when running from live CD on MacBook Air
::Use MacBook Ethernet Dongle for Networking
===Install_Sugar-desktop_0.88===
: Do this only if you install to a HD; USB or in VirtualBox 4.0 -will not work if running from the Booted CD
:: Follow link: http://wiki.sugarlabs.org/go/Trisquel_On_A_Sugar_Toast#Install_Sugar-desktop_0.88_.22SWEETS.22

==Bootable DVD of f14 for MacBook Air==
:'''livecd-fedora-live-desktop-201101311532.iso Boots into F14 Gnome Desktop using the "C" key on MacBook Air and a Burned DVD'''
https://bugzilla.redhat.com/show_bug.cgi?id=528232#c85
-------------------------------------------------------
Luke Macken <mailto:lmacken <at> redhat_com> 2011-01-31 18:08:44 EST
I updated our patch to support the following models:
iMac9,1
MacBookAir2,1
MacBookPro5,5
MacBookPro6,2
I also spun up an F14 x86_64 live image with this patch. Testing appreciated.
http://lewk.org/livecd-fedora-live-desktop-201101311532.iso

:Use External USB DVD/CD Drive hold down the "C" key on MacBook Air until booted from DVD
::Works nicely. NO Wireless or Magic Mouse when running from live CD on MacBook Air
::Use MacBook Ethernet Dongle for Networking

* Installs to VirtualBox 4.02 OSX correctly 02/01/2011 satellit
:NOTE: Will only run on x86_64 bit hardware (including Mac's)
: First Run When started after install
# Firstboot
# smolt
# gdm login
===To install sugar-desktop===
: In root terminal:
yum groupinstall sugar-desktop (73 packages; Installed Size: 229 M download size 95 M)
yum install sugar-emulator

: Fedora 14 Sugar 0.90.1
: Sugar asks for users keychain password to start

===dd write to USB===
::'''THIS IS AN EXPERIMENT'''
# dd if=livecd-fedora-live-desktop-201101311532.iso of=/dev/sdg
2000896+0 records in
2000896+0 records out
1024458752 bytes (1.0 GB) copied, 279.742 s, 3.7 MB/s
* USB Will not boot on Mac Air with or without startup boot CD
* USB Boots fine on ACER ASPIRE ONE Netbook and wireless works.
===Install to Hard Disk (8 GB USB)===
::'''THIS IS AN EXPERIMENT'''
Boot MacBook Air from Burned DVD (livecd-fedora-live-desktop-201101311532.iso) with Mac Air external DVD/CD reader by holding down "C" key on power on until it boots
Select low graphics on Boot Menu
Insert 8 GB USB into 2nd USB slot on Mac (Format fat 32 labeled FEDORA)
Select Install to Hard Disk Icon
Basic install
Custom
device sdb is USB (FEDORA)
Erase sdb1
Create /boot ext4 500
Create / ext4 Balance of sdb
Forward
Grub on sdb1
Copy files to make USB
* '''Does Not Boot from USB''' by holding down "C" key on power on until it boots
* Tried Boot CD but it fails to boot USB "No root device found"

==Macbook Pro==

Matt Wronkiewicz wrote:

If anyone else is interested, I put together a boot helper for
Mirabelle. Burned to a CD, it enabled booting a USB stick on my
MacBook Pro. The stick was partitioned with the plain old MBR format
and labeled "FEDORA". I also got both VMware Fusion and VirtualBox to
boot the USB stick using this boot helper ISO. The soas-2-boot ISO
sort of works with Mirabelle sticks, but they have different kernel
versions so modules don't load, thus no networking. That is fixed in
this build.

<http://www.wronkiewicz.net/soas-3-boot-test.iso>
revised with low graphics boot line
<http://www.wronkiewicz.net/soas-3-boot-test2.iso>

==Installation to HD, USB hard drive, and USB/SD flash drives==
The [[LiveOS image]] technology uses compression to install operating systems on smaller discs such as CD-ROMs and small USB/SD flash storage devices.

The extra compression layer may be avoided by installing to an uncompressed file system by one of the methods itemized in the first section below:

=== Uncompressed file systems ===
# livecd-iso-to-disk script using the --skipcompress option
#: {{Code|livecd-iso-to-disk --skipcompress --overlay-size-mm <NN> --home-size-mb <NN> --delete-home --unencrypted-home /path/to/isofile/or/mounted/image /dev/sd'''?'''1}}
#: See [[Sugar_on_a_Stick/Linux]].
<div style="font-size: 1.0em; background: #ffeec4; padding: 1px; border: 1px solid #cde7a8">
# zyx-liveinstaller <from Ferminal>[[Sugar_on_a_Stick/ZyX-LiveInstaller]]
#* creates real file structure on USB or HD (without rebooting)
#* name and color selection (and ssh keys remain the same)
#*:This can be a problem for using it for distribution
# liveinst (Anaconda)<from Terminal> [[Sugar_on_a_Stick/Linux/Non-compressed_Fedora#Use_liveinst_command_in_terminal]]
#* installs to HD or USB stick
#* If you make an .img file from the USB before running "firstboot", it becomes a good way to duplicate the sticks.
# Net install CD [[Sugar_on_a_Stick/Linux/Non-compressed_Fedora#Make_your_OWN_Custom_SUGAR-DESKTOP_USB_Boot_Stick]]
#* need a fast Internet connection
#* very slow install(6+ hours for USB)
#* allows custom install of sugar-desktop only or Gnome/KDE + Sugar
#* If you make an .img file from the USB before running "firstboot", it becomes a good way to duplicate the sticks.
::::Copy : dd if=/dev/sd(x) of=xxxxxx.img [1] see below
::::Duplicate: dd if=xxxxxx.img of=/dev/sd(x)
</div>

===Compressed file systems on USB/SD devices===

# script with .iso file - See [[Talk:SoaS_Blueberry_Instructions]].
# live-usbcreator application
#* Download the latest version of the Fedora LiveUSB Creator from http://fedorahosted.org/liveusb-creator and extract it.
#* Plug a blank target USB flash drive (or SD Card) into your computer (minimum 1-gigabyte).
#* Launch LiveUSB Creator.
#* Select Sugar on a Stick v2 Blueberry in the drop-down menu on the upper-right side to download the liveUSB disk image. Alternatively, download Blueberry here, then hit the Browse button and select the downloaded file.
#* Adjust the Persistent Storage slider. This enables you to save the child's work in Sugar onto the device.
#* Select your flash drive as the target and click the Create Live USB button.
#* Wait for the process to finish, then close the LiveUSB Creator program.
#* Stop your flash drive using the Safely Remove Hardware dialog and eject it.
# other Linux distributions [[Sugar_on_a_Stick/Linux]]
<div style="font-size: 1.0em; background: #ffeec4; padding: 1px; border: 1px solid #cde7a8">
*4 dd write to USB '''(Very DANGEROUS-can destroy your Hard Drive)'''
::USE "mount" command to determine USB device name (ie: /dev/sdb;/dev/sdc/;/dev/sdd ...etc) [1]
::Fastest way to write a LIVE usb (about 3.5 minutes for a Soas.iso)
::No persistence
:: Functionally identical to Burned CD
::Great for installation when there is no CD/DVD drive (netbooks)
: Example when live.iso is on Desktop (root terminal):
:::cd Desktop
:::dd if=soas-i386-20101004.16.iso of=/dev/sd(x) [1]
:::1024000+0 records in
:::1024000+0 records out
:::524288000 bytes (524 MB) copied, 214.199 s, 2.4 MB/s
</div>

==Duplication of USB/SD .img files==
# dd copy of USB/SD <from terminal>[[Sugar_on_a_Stick/Linux/Non-compressed_Fedora#Duplication_of_USB_Sticks]] Autologon [[Sugar_on_a_Stick/Linux/Non-compressed_Fedora#AUTO_Login_to_SUGAR]]

=='''Upgrade an XO-1 to Sugar 0.84 with Fedora 11 and Gnome'''==

'''WARNING: THIS WILL OVERWRITE YOUR NAND in the XO-1 with the new OS.'''

Please read the instructions found [http://www.olpcnews.com/forum/index.php?topic=4768.msg31772#msg31772%3E on the OLPC News site]. Refer to Message #3: "How to install". You must have a Developer Key, and security disabled on your OLPC.

* Please note: Software has been updated since that posting. The latest Software is available here:
<big><code>http://people.sugarlabs.org/bernie/olpc/f11-xo1-py/?C=M;O=D</code></big>
* Note: Be sure to plug in your laptop using its AC charger to ensure that the installation process is completed. (The firmware will not be updated under battery power.)

* Put the two corresponding files (.img and .crc) of the same version-number on a bootable USB/SD device formated as FAT32.
* Add your [http://wiki.laptop.org/go/Activation_and_developer_keys Developer Key] to the USB.
*'''Be certain to disable OLPC-security first as per the instructions.''' You can control this, when Open firmware prompts: "No WP Tag" it means "is already disabled".
* Connect your device to the OLPC
* Boot while holding down the "checkmark button".
When Open Firmware counts down 3 seconds "...before automatic startup", push the "escape button", to get to the "OK" Open Firmware prompt.

:* If the files were downloaded onto an USB stick:
type
{{Code|probe-usb}}
Press Enter.
Control if Open Firmware has detected your device. (A "found" usb when probing, e.g., usb:/***/disk means you have to name it in the command: {{Code|copy-nand disk:\os***py.img}})
Then type
{{Code|copy-nand usb:\os***py.img}}
and press Enter.
(note: replace *** with your actual versionnumber/filename.)

:* If the files were downloaded onto a SD card:
type
{{Code|copy-nand sd:\os***py.img}}
and press Enter.

* when the colored points aren't changing anymore, and Open Firmware says: OK
disconnect your USB/SD device and type
{{Code|reboot}}

When there happens a failure message (or no at all but no booting-process), try to overwrite your files a second time, try to re-download your file (eg "crc miscompare"), try to reformat your usb-stick (eg "is not a multiple of the nand erase block size"), try googling... (one time it helped to remove batteries for approximately 10 seconds. There are anecdotal cases where this resets the electronic controller that has unhung.)
try!
In the case of success: '''Enjoy!'''

'''WARNING: THIS WILL OVERWRITE YOUR NAND in the XO-1 with the new OS.'''

==Download Questions==

* This page still recommends the Fedora LiveUSB installation method as the PREFERRED method for Windows SOAS, despite the known problem of eventual overlay corruption. At a minimum, the Windows section should state that the Live-USB method is easiest but should be used only for temporary SOAS sticks or for evaluation purposes, and NOT for long-term sticks. See [[Sugar on a Stick]]/Windows, Live USB - "(This installation method is NOT recommended for LONG-TERM usage of Sugar on a Stick!! Catastrophic data corruption may occur when the USB stick gets full! See why.) "

Talk:Sugar on a Stick/Windows

2013-12-10T17:36:23Z

David Kergyl: Corrected placement of Recommended overlay and home sizes question.

==Introduction==
Can someone explain a little more in the intro as to how sugar on a stick will work with a windows machine? Do you boot on it? Is it some sort of virtual machine? Is SoaS for windows a linux OS?
[[User:Harriska2|Harriska2]]
: See ideas emerging on this topic at [[Sugar on a Stick/Roadmap#Use cases]] --[[User:FGrose|FGrose]] 19:06, 26 March 2009 (UTC)
== Caroline's Repeatable Process for Creating Sticks ==
(This may be out of date.)
This is the process I (Caroline Meeks) use. Some of the things I do maybe superstition, but here is it.

=== Preparation: ===

# Download and install version 3.6.5 live usb creator for XP
# Download the iso snapshot you want to create - You only have to download it once.

=== For Each Stick ===

# Insert a 1 or 2 GB Stick
# Delete files so that you have 700 MiB or more of space available.
#: (The formatting step is not needed, but may help if other methods don't work) Format it using FAT. If it has anything on it it will be completely erased so you can reuse sticks.
#: See [[olpc:How to Damage a FLASH Storage Device]] before formatting. The 'Stick' probably came with a FAT file system that the Fedora LiveUSB Creator will use. You can even leave some of your files on the drive. You may want to try using the native drive formatting to see if it works before reformatting the drive.
# Name the volume FEDORA (The File Manager's properties, General tab panel will let you rename a volume.)
#: This does not seem to be necessary with current version.
# Open the live USB creator
# Click Browse and find your snapshot
# Move the slider for persistent storage but don't use absolutely everything on the stick. These days I use about 500 MB for a 1 GB Stick
# Burn the stick. It takes about 15 minutes or so for me
# Close the live USB creator
# Eject the stick
# Create a boot-helper CD that matches your snapshot (I use my mac for that, but I've never heard of problems so any way of creating a LiveCD should work)

==For Windows only users==

Hi,

Windows has at least two different levels of "format". The instructions are not clear as to which to use or not use.

One is FDISK, usually run from DOS, and seems like it should be avoided because it will muck with the partition boundaries.

Another is the FORMAT of the "File Manager", usually accessed by right clicking on the device.("Explore" to the device, right click, select "Format...". Within that choice is a "Quick Format" option which may be good or bad to use with a flash device.

Could someone who knows make the instructions a bit clearer????

MWTalbutt -- 29-Jun-2009

: The Windows instructions no longer recommend formatting the USB device. --[[User:FGrose|FGrose]] 20:06, 29 June 2009 (UTC)

: Thanks FGrose! They are slightly clearer - at least it says something like "Do Not Do unless fails without." Perhaps the detail I was looking for belongs on the http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device page? MWTalbutt

* Recommended overlay and home sizes -
Execute the Linux command line: /livecd-iso-to-disk --reset-mbr --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-

- Shouldn't these sizes be bigger for 4 GB and 8GB USB sticks?

===[SoaS] Problem with Mirabelle and USB Boot===
soas lists 07/01/2010 posted by satellit

OK,

To prevent it name the sticks Fedora prior to putting the image on them. (This step should be added to the online instructions.)

Now, if you did not change the name and need to modify the syslinux.cfg, change the following lines: (you will have a different UUID#)

append initrd=initrd0.img root=live:UUID=3D4E-8E71 rootfstype=vfat rw liveimg overlay=UUID=3D4E-8E71 quiet rhgb rd_NO_LUKS rd_NO_MD

append initrd=initrd0.img root=live:UUID=3D4E-8E71 rootfstype=vfat rw liveimg overlay=UUID=3D4E-8E71 quiet rhgb check

to

append initrd=initrd0.img root=LABEL=FEDORA rootfstype=vfat rw liveimg overlay=LABEL=FEDORA quiet rhgb rd_NO_LUKS rd_NO_MD

append initrd=initrd0.img root=LABEL=FEDORA rootfstype=vfat rw liveimg overlay=LABEL=FEDORA quiet rhgb check

I tested this fix and it works.

Marc marckarasek@gmail.com

==putting sugar around a stick (with fedora's help)==

Hi,

just a heads up about where we are regarding installation of Soas:

- on Windows we are very well, it's reported that liveusb-creator
works well even for XOs,

- on Linux, latest releases of liveusb-creator weren't working at all,
but people are working to fix that on Fedora 10 (thanks Kushal!). On
other distros, seems like recent Liveusb-creator won't work due to new
dependencies included :(

- about livecd-iso-to-disk.sh on all linux flavors, it isn't working
currently for Soas2 because Rawhide requires that a more recent
version of syslinux (3.73) is installed
(http://dev.sugarlabs.org/ticket/643). The good news is that we have a
workaround (thanks Elena!).

- also, livecd-iso-to-disk.sh will fail to install correctly an image
that can boot on XOs because of http://dev.sugarlabs.org/ticket/644 .
It has been reported upstream.

- and also, livecd-iso-to-disk.sh will fail to install correctly an
image that can boot on XOs because it seems to require reading a
squashfs image in a format that only very recent kernels (2.6.29) can
read. No idea what we can do here, but maybe we don't really need to
read that image from the computer that makes the installation?
Otherwise, how can liveusb-creator do the installation for XOs on
windows?

Any help appreciated.

Thanks,

Tomeu (26 March 2009)

==bit more help needed please==
I haven't got it to boot yet, and maybe my lack of computing experience will help improve the instructions for non-sysadmins.
a) may be worth clarifying that burning a .iso is not just putting a data file on a disk but 'burn compilation' or somesuch.
b)'file manager properties' - don't see that with Windows 2000. Using 'rename' seems to have problems; put it in another computer and the name did not show as FEDORA, though that was the 'label'.
c) let the computer reboot from the CD; ain't got that far yet.

Still to work out what I am doing wrong, but the instructions and context here are for linux hackers and geeks; a long way to go before it looks like an education project, I am afraid.

Brian 25 July 2009
:Please see the amended instructions. Renaming is not required with current version of the installer. The Fedora Live USB Creator transfers the disc image to the USB drive. --[[User:FGrose|FGrose]] 00:57, 26 July 2009 (UTC)

Talk:Sugar on a Stick/Windows

2013-12-10T17:32:15Z

David Kergyl: /* For Windows only users */ Add comment re: recommended overlay and home sizes.

==Introduction==
Can someone explain a little more in the intro as to how sugar on a stick will work with a windows machine? Do you boot on it? Is it some sort of virtual machine? Is SoaS for windows a linux OS?
[[User:Harriska2|Harriska2]]
: See ideas emerging on this topic at [[Sugar on a Stick/Roadmap#Use cases]] --[[User:FGrose|FGrose]] 19:06, 26 March 2009 (UTC)
== Caroline's Repeatable Process for Creating Sticks ==
(This may be out of date.)
This is the process I (Caroline Meeks) use. Some of the things I do maybe superstition, but here is it.

=== Preparation: ===

# Download and install version 3.6.5 live usb creator for XP
# Download the iso snapshot you want to create - You only have to download it once.

=== For Each Stick ===

# Insert a 1 or 2 GB Stick
# Delete files so that you have 700 MiB or more of space available.
#: (The formatting step is not needed, but may help if other methods don't work) Format it using FAT. If it has anything on it it will be completely erased so you can reuse sticks.
#: See [[olpc:How to Damage a FLASH Storage Device]] before formatting. The 'Stick' probably came with a FAT file system that the Fedora LiveUSB Creator will use. You can even leave some of your files on the drive. You may want to try using the native drive formatting to see if it works before reformatting the drive.
# Name the volume FEDORA (The File Manager's properties, General tab panel will let you rename a volume.)
#: This does not seem to be necessary with current version.
# Open the live USB creator
# Click Browse and find your snapshot
# Move the slider for persistent storage but don't use absolutely everything on the stick. These days I use about 500 MB for a 1 GB Stick
# Burn the stick. It takes about 15 minutes or so for me
# Close the live USB creator
# Eject the stick
# Create a boot-helper CD that matches your snapshot (I use my mac for that, but I've never heard of problems so any way of creating a LiveCD should work)

==For Windows only users==

Hi,

Windows has at least two different levels of "format". The instructions are not clear as to which to use or not use.

One is FDISK, usually run from DOS, and seems like it should be avoided because it will muck with the partition boundaries.

Another is the FORMAT of the "File Manager", usually accessed by right clicking on the device.("Explore" to the device, right click, select "Format...". Within that choice is a "Quick Format" option which may be good or bad to use with a flash device.

Could someone who knows make the instructions a bit clearer????

MWTalbutt -- 29-Jun-2009

: The Windows instructions no longer recommend formatting the USB device. --[[User:FGrose|FGrose]] 20:06, 29 June 2009 (UTC)

: Thanks FGrose! They are slightly clearer - at least it says something like "Do Not Do unless fails without." Perhaps the detail I was looking for belongs on the http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device page? MWTalbutt

===[SoaS] Problem with Mirabelle and USB Boot===
soas lists 07/01/2010 posted by satellit

OK,

To prevent it name the sticks Fedora prior to putting the image on them. (This step should be added to the online instructions.)

Now, if you did not change the name and need to modify the syslinux.cfg, change the following lines: (you will have a different UUID#)

append initrd=initrd0.img root=live:UUID=3D4E-8E71 rootfstype=vfat rw liveimg overlay=UUID=3D4E-8E71 quiet rhgb rd_NO_LUKS rd_NO_MD

append initrd=initrd0.img root=live:UUID=3D4E-8E71 rootfstype=vfat rw liveimg overlay=UUID=3D4E-8E71 quiet rhgb check

to

append initrd=initrd0.img root=LABEL=FEDORA rootfstype=vfat rw liveimg overlay=LABEL=FEDORA quiet rhgb rd_NO_LUKS rd_NO_MD

append initrd=initrd0.img root=LABEL=FEDORA rootfstype=vfat rw liveimg overlay=LABEL=FEDORA quiet rhgb check

I tested this fix and it works.

Marc marckarasek@gmail.com

* Recommended overlay and home sizes -
Execute the Linux command line: <div style="padding: 1em; border: 1px dashed #2F6FAB; background-color: #FBFBFB; margin: 1em 0px 1em 0em; font-family: Courier;">./livecd-iso-to-disk --reset-mbr --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-

- Shouldn't these sizes be bigger for 4 GB and 8GB USB sticks?

==putting sugar around a stick (with fedora's help)==

Hi,

just a heads up about where we are regarding installation of Soas:

- on Windows we are very well, it's reported that liveusb-creator
works well even for XOs,

- on Linux, latest releases of liveusb-creator weren't working at all,
but people are working to fix that on Fedora 10 (thanks Kushal!). On
other distros, seems like recent Liveusb-creator won't work due to new
dependencies included :(

- about livecd-iso-to-disk.sh on all linux flavors, it isn't working
currently for Soas2 because Rawhide requires that a more recent
version of syslinux (3.73) is installed
(http://dev.sugarlabs.org/ticket/643). The good news is that we have a
workaround (thanks Elena!).

- also, livecd-iso-to-disk.sh will fail to install correctly an image
that can boot on XOs because of http://dev.sugarlabs.org/ticket/644 .
It has been reported upstream.

- and also, livecd-iso-to-disk.sh will fail to install correctly an
image that can boot on XOs because it seems to require reading a
squashfs image in a format that only very recent kernels (2.6.29) can
read. No idea what we can do here, but maybe we don't really need to
read that image from the computer that makes the installation?
Otherwise, how can liveusb-creator do the installation for XOs on
windows?

Any help appreciated.

Thanks,

Tomeu (26 March 2009)

==bit more help needed please==
I haven't got it to boot yet, and maybe my lack of computing experience will help improve the instructions for non-sysadmins.
a) may be worth clarifying that burning a .iso is not just putting a data file on a disk but 'burn compilation' or somesuch.
b)'file manager properties' - don't see that with Windows 2000. Using 'rename' seems to have problems; put it in another computer and the name did not show as FEDORA, though that was the 'label'.
c) let the computer reboot from the CD; ain't got that far yet.

Still to work out what I am doing wrong, but the instructions and context here are for linux hackers and geeks; a long way to go before it looks like an education project, I am afraid.

Brian 25 July 2009
:Please see the amended instructions. Renaming is not required with current version of the installer. The Fedora Live USB Creator transfers the disc image to the USB drive. --[[User:FGrose|FGrose]] 00:57, 26 July 2009 (UTC)

Sugar on a Stick/Windows

2013-12-10T17:27:23Z

David Kergyl: /* with Microsoft Windows */ Switched order of Windows installation methods to de-emphasize using LiveUSB, in view of unsolved overlay corruption problem, and added emphasis on warming. The method formerly numbered 1 is now number 2.

<noinclude>
[[Category:HowTo]]

== Introduction ==

This page is designed to help you to put your [[Sugar on a Stick]] image on a thumbdrive using Microsoft Windows. If you have questions, trouble or feedback, please let us know on the [[Talk:Sugar on a Stick|Sugar on a Stick talk]] page. If you can improve these instructions, please edit the page and do so!</noinclude>
=== with Microsoft Windows ===
[[File:Windows.gif|link=Sugar on a Stick/Windows]]
There are three ways to do this:

{{Anchor|Burn a CD-ROM}}
* '''1. Burn a CD-ROM disc, boot from it, then run the script, ''livecd-iso-to-disk'''''
*# Use [http://windowsteamblog.com/blogs/windowsexperience/archive/2009/04/13/burn-iso-images-natively-in-windows-7.aspx Windows 7 built-in Disk Image Burner] or a free utility, like [http://www.imgburn.com/ ImgBurn], to write the downloaded Sugar on a Stick .iso file onto a blank CD.
*# Insert a USB flash drive (or SD Card [[#Notes|Notes]]) with 2 GB or more of free space into your computer.
*# Boot your computer with the CD-ROM disc. You probably need to press F1, F10, F12, Esc, or a similar key as the computer starts up in order to set the boot source for your computer to the CD-ROM device.
*# A successful boot will take you into ''Sugar on a Stick''. You can From there, open the Terminal Activity, [[File:Activity-terminal.png|bottom|link=http://en.flossmanuals.net/terminal]], from the Home view.
*# Click the 'Become root' icon, [[File:Activity-become-root.svg]], to gain administrative permissions in the Terminal session.
*# Change the working directory to {{Code|/run/initramfs/live/LiveOS}}
*#: (Versions earlier than Fedora 17 would use {{Code|/mnt/live/LiveOS}} or {{Code|/LiveOS}}.)
*# ''Be certain of your USB/SD '''s'''csi '''d'''rive node name (such as sda, sdb, etc.) and partition (such as 1, 2, etc.), for example,'' {{Code|/dev/sd'''b'''1}}.
*#* The {{Code|df -Th}} command shows your device filesystem on a device node, for example, /dev/sda1, mounted on a directory [[wikipedia:Mount (computing)|mount point]], such as /run/media/<AccountName>/<USBdeviceManufacturer>
<ul><ul><ul><ul>
{{Show|You should see something like the following:
|<pre>
[root@localhost LiveOS]# df -Th
Filesystem Type Size Used Avail Use% Mounted on
rootfs rootfs 4.0G 2.5G 1.5G 63% /
devtmpfs devtmpfs 1.6G 0 1.6G 0% /dev
tmpfs tmpfs 1.6G 84K 1.6G 1% /dev/shm
tmpfs tmpfs 1.6G 1.2M 1.6G 1% /run
/dev/sr0 iso9660 509M 509M 0 100% /run/initramfs/live
/dev/mapper/live-rw ext4 4.0G 2.5G 1.5G 63% /
tmpfs tmpfs 1.6G 0 1.6G 0% /sys/fs/cgroup
tmpfs tmpfs 1.6G 0 1.6G 0% /media
varcacheyum tmpfs 1.6G 0 1.6G 0% /var/cache/yum
tmp tmpfs 1.6G 40K 1.6G 1% /tmp
vartmp tmpfs 1.6G 0 1.6G 0% /var/tmp
/dev/sda1 vfat 3.7G 2.1G 1.7G 56% /run/media/liveuser/TOSHIBA
</pre>}}</ul></ul></ul>
<ol start="8">
<li> Unmount the USB device filesystem: {{Code|umount /run/media/MyAccount/MyUSBdiscMountPoint}}</li>
<li> Execute the Linux command line: <div style="padding: 1em; border: 1px dashed #2F6FAB; background-color: #FBFBFB; margin: 1em 0px 1em 0em; font-family: Courier;">./livecd-iso-to-disk --reset-mbr --overlay-size-mb '''500''' --home-size-mb '''900''' --delete-home --unencrypted-home /run/initramfs/livedev /dev/sd'''?'''1</div>
: (Versions earlier than Fedora 17 would use {{Code|/dev/live}} or {{Code|/dev/sr0}} instead of {{Code|/run/initramfs/livedev}}.)</li>
<li> Shutdown the physical machine.</li>
<li> Reboot from the newly-installed Live USB with Sugar on a Stick.</li>
</ol></ul>

* '''2. Use Fedora Live USB Creator'''
*: (This installation method is NOT recommended for LONG-TERM usage of Sugar on a Stick!! Catastrophic data corruption may occur when the USB stick gets full! [[fedora:LiveOS_image#Home_filesystem|See why.]])
*# Download the Live USB Creator from [http://fedorahosted.org/liveusb-creator/ Fedora].
*# Insert a USB flash drive (or SD Card [[#Notes|Notes]]) with 2 GB or more of free space into your computer.
*# Launch Live USB Creator.
*# Select the 'Browse' button to 'Use existing Live CD' and find the downloaded .iso file image on your system.
*# Adjust the Persistent Storage slider. This enables you to save changes to the system and additional Sugar Activities onto the device.
*# Select your flash drive as the target, and click the '''Create Live USB''' button.
*# Wait for the process to finish, then close the Live USB Creator program.
*# Stop your flash drive with the '''Safely Remove Hardware and Eject Media''' notification area icon dialog, and eject it.
::: See a [[Tutorials/Installation/Create_a_SoaS_v7_Live_USB_in_Windows|screenshot tutorial]] for this.
::: See a [http://www.youtube.com/watch?v=ieIj4aECk88 video] of an earlier version of this process.

* '''3. Launch a virtual machine with the Sugar on a Stick .iso file, then run the script, ''livecd-iso-to-disk'''''
*# Download and install [[VirtualBox]] (for example; you could do something similar with another vm).
*# Create a new virtual machine.
*# Choose Linux for the Operating System and Version Fedora (64 bit) if available, or Fedora, on systems lacking 64-bit functionality.
*# Attach the Sugar on a Stick .iso file as a CD in the Storage Section
*# Insert a USB storage device into your physical computer and enable the VirtualBox USB controller. Then add a filter to recognize the inserted device in the USB section of the VirtualBox machine setup.
*# Start the new virtual machine.
*# Verify that the USB device is recognized in the running virtual machine.
*#* Your device appears in the hover box for the USB stick icon in the virtual machine bottom frame.
*#* {{Code|df -Th}} shows your device filesystem on a device node, for example, /dev/sda1, mounted on a directory [[wikipedia:Mount (computing)|mount point]], such as /run/media/<AccountName>/<USBdeviceManufacturer>
<ul><ul><ul>
{{Show|You should see something like the following:
|<pre>
[root@localhost LiveOS]# df -Th
Filesystem Type Size Used Avail Use% Mounted on
rootfs rootfs 4.0G 2.5G 1.5G 63% /
devtmpfs devtmpfs 1.6G 0 1.6G 0% /dev
tmpfs tmpfs 1.6G 84K 1.6G 1% /dev/shm
tmpfs tmpfs 1.6G 1.2M 1.6G 1% /run
/dev/sr0 iso9660 509M 509M 0 100% /run/initramfs/live
/dev/mapper/live-rw ext4 4.0G 2.5G 1.5G 63% /
tmpfs tmpfs 1.6G 0 1.6G 0% /sys/fs/cgroup
tmpfs tmpfs 1.6G 0 1.6G 0% /media
varcacheyum tmpfs 1.6G 0 1.6G 0% /var/cache/yum
tmp tmpfs 1.6G 40K 1.6G 1% /tmp
vartmp tmpfs 1.6G 0 1.6G 0% /var/tmp
/dev/sda1 vfat 3.7G 2.1G 1.7G 56% /run/media/liveuser/TOSHIBA
</pre>}}</ul></ul>
<ol start="9">
<li> Continue from step #4 in the '''Burn a CD-ROM disc''' section above.</li>
<li> Shutdown the virtual machine.</li>
<li> Reboot your physical computer from the newly-installed Live USB with Sugar on a Stick.</li>
</ol>
</ul>

===Notes===
A Secure Digital (SD) card may not be marked as a bootable device. To check this, use these instructions at a Linux terminal or console:
{{:Sugar on a Stick/Linux/bootable device}}

Activities/Browse

2013-12-10T16:41:53Z

David Kergyl: Added cross-reference to Educational Tools.

<noinclude>{{Translations | [[Activities/Browse|english]] |}}
[[Category:Activities|Browse]]
</noinclude>

==Where to get Browse==
Browse is a part of the [[Taxonomy#Fructose: The set of demonstration activities|Fructose, ''the set of demonstration activities'']], and therefore included as part of the standard Sucrose distribution.

[http://activities.sugarlabs.org/en-US/sugar/addon/4024 Activity] | [http://git.sugarlabs.org/projects/browse Source] | [http://download.sugarlabs.org/sources/sucrose/fructose/Browse Source tarball]| [[OLPC:Browse]] |
{{Iframe|[http://en.flossmanuals.net/browse Browse Activity Manual] | http://en.flossmanuals.net/browse| 940|800|1}}
Tickets in Trac: [http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&groupdesc=1&group=milestone&component=Browse&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=version&col=severity&col=resolution&col=status_field&col=reporter&col=time&col=changetime Sugar Labs] | [http://dev.laptop.org/query?status=assigned&status=new&status=reopened&groupdesc=1&group=milestone&max=150&component=browse-activity&order=id&col=id&col=summary&col=status&col=owner&col=type&col=next_action&col=changetime#no2 OLPC] |

=== User tips ===
* When downloading, .xos for example, you have to click 'ok' on the download status alert to view the status of a new download.
http://www.youtube.com/watch?v=CFU88Fve6qk 
* See [[Educational Tools]] for educational websites to visit in Browse.

=== i18n ===
(See [http://translate.sugarlabs.org/ our Pootle server] for details about how to translate Browse into your language.)

==Background==
''still to come''

==Release notes==
{{Transclude|collapsed=collapsed|note='''[[0.86/Browse]]''' transcluded:|0.86/Browse}}
{{Transclude|collapsed=collapsed|note='''[[0.84/Browse]]''' transcluded:|0.84/Browse}}

Education Team/Lesson Plan resources

2013-12-10T16:20:21Z

David Kergyl: /* Related topics */ Add cross-reference to Educational Tools

== Lesson plan templates/formats ==

* sugar [[Lesson plan template]]
* A few different ones: http://www.internet4classrooms.com/links_grades_kindergarten_12/lesson_plans_templates.htm
* others?

== Lesson plans ==

*http://www.nea.org/tools/LessonPlans.html
*http://www.curriki.org/xwiki/bin/view/Main/Browse
*http://www.halcyon.com/marcs/lessons.html
*http://www.thegateway.org/
*http://www.internet4classrooms.com/lesson.htm
*http://learning.blogs.nytimes.com/category/lesson-plans/
*http://www.mcrel.org/lesson-plans/
*http://www.bbc.co.uk/schools/teachers/ ("Lesson Plans and Worksheets" section)
**http://www.bbc.co.uk/schools/teachers/keystage_1/topics/maths_ks1.shtml (for example)
*http://wiki.laptop.org/go/Category:Hackety_Lesson_Plan
*http://www.awesomelibrary.org/Library/Materials_Search/Lesson_Plans/Science.html

== Lesson plan ideas ==

* New group just created at http://www.curriki.org/xwiki/bin/view/Group_SugaronaStick/. Looking for interested teachers to contribute lesson plans to grow this into a repository. If you need a lesson plan template [[Media:Sugar_Lesson_Plan_Template.dotx|this one]] may be used as is or is easily adapted.

* [http://dir.yahoo.com/education/k_12/teaching/lesson_plans/ Yahoo Directory of Lesson Plans]

* dmoz.org lesson plans:
** http://www.dmoz.org/Arts/Education/Language_Arts/Lesson_Plans_and_Reproducibles/
** http://www.dmoz.org/Reference/Education/K_through_12/Educators/Lesson_Plans/
** meta: [http://search.dmoz.org/cgi-bin/search?search=lesson%20plans&utf8=1&locale=en_gb&morecat=1 dmoz.org Directory of Lesson Plans]

*EtoysIllinois has a great collection of Etoys projects and resources for teachers for curriculum integration
**http://www.squeakcmi.org/library.php
**http://www.squeakcmi.org/resources.php

*List of free teaching software (german)
**http://wiki.skolelinux.de/LernSoftware maintained by the German team of skolelinux
**http://www.skolelinux.de
*Skolelinux has integrated using the KDE-Education project
**http://edu.kde.org/
*Teacher training project (german)
**http://www.seminarix.org/files/start.html

*Collection of free teaching software with tagged OS and screenshots, more than 80 pages in PDF
**http://www.skolelinux.de/download/education_FOSS_catalog.pdf

*How about some outreach to a group committed to produce curriculum materials for grades 4 to 12 using Python and E-toys for use in South Africa? They are funded by the Shuttleworth Foundation (Ubuntu money and major commitment to open everything—being phased out, unfortunately).
**http://www.kusasa.org

*Try to seek aligned interests with any of the other open and collaborative efforts like Free High School Science Texts, who's goal is to develop a set of complete textbooks for Maths, Physics and Chemistry for grades 10-12 will be completed by early 2008, all under GDFL licensing.
**http://www.fhsst.org/

*Interesting on-line high school physics course
**http://online.cctt.org/

*http://www.free.ed.gov/

*http://computerlearning.org/

*Teachers pay Teachers - an open marketplace for educators (some free content, some paid)
**http://www.teacherspayteachers.com/Home

*Anytime Anywhere Learning Foundation (AALF)
**http://www.aalf.org/
:AALF is a 501(c) 6 not for profit association whose mission is to serve as an advocacy vehicle for anytime, anywhere learning.

*http://www.nea.org/tools/SubmitYourLesson.html

Etoys shares features with other drag and drop programming environments such as Game Maker and Click & Play. The lesson plans, samples and pedagogies developed in classrooms can be easily adapted to Etoys
* http://www.mindtools.tased.edu.au/default.htm
* http://www.users.on.net/~billkerr/g/int.htm
* http://rupert.id.au/schoolgamemaker/

"ReadWriteThink is a partnership between NCTE, the International Reading Association (IRA), and the MarcoPolo Education Foundation, established in April of 2002."
* http://www.ncte.org/profdev/online/rwt BROKEN LINK

MERLOT - Multimedia Educational Resources for Learning and Online Teaching
*http://www.merlot.org/merlot/index.htm

----
**Some papers by Alan Kay

* http://www.vpri.org/pdf/OLPCCountries_RN-2007-006-a.pdf
* http://www.vpri.org/pdf/etoys_n_authoring.pdf
* http://www.vpri.org/pdf/etoys_n_learning.pdf
----

*Tapping Epistemological Resources for Learning Physics
** http://www.informaworld.com/smpp/content~content=a785041701~db=all

*Naive Physics Reasoning: A Commitment to Substance-Based Conceptions
** http://www.informaworld.com/smpp/content~content=a783760369~db=all

*On the Nature of Naïve Physics
** http://www.springerlink.com/content/kl44571021758m33/

*Open source 2D physics engine Box2D
** http://box2d.org
and the Physics activity (and the Elements/pybox2d development being done in its branch)
** http://wiki.laptop.org/go/Physics_%28activity%29
** http://dev.laptop.org/git?p=activities/physics

== Related topics ==
* [[Replacing Textbooks]]
* [[Open Education Resources]]
* [[Educational Tools]] - Useful educational websites to visit.

Educational Tools

2013-12-10T16:07:53Z

David Kergyl: Add Starfall image link, with permission from http://www.starfall.com/n/N-info/helpdesk.htm?n=educators.

<h3>Hello! This is a list of some of the best educational tools/sites found on the internet. </h3>
(As recommended by community members -- this list is not endorsed by Sugar Labs)

Feel free to enjoy any and all of them, and please, if you know of any more sites that might be beneficial to add here, please add it! This is a community list.

[http://khanacademy.org khanacademy.org] - Watch thousands of micro-lectures on topics ranging from history and medicine to chemistry and computer science! 
[http://freerice.com freerice.com] - Help end world hunger by correctly answering multiple-choice quizzes on a wide variety of subjects! 
[http://unplugthetv.com unplugthetv.com] - ''[Requires Flash]'' Randomly selects an educational video to watch instead of useless drivel. 
[http://coursera.org coursera.org] - Educational site that works with universities to get their courses on the internet, free for you to use! 
[http://lizardpoint.com lizardpoint.com] - ''[Requires Flash]'' A collection of browser-based games and the like to improve knowledge of geography, math, and such. 
[http://ted.com ted.com] - ''[Requires Flash]'' Collection of TED (Technology, Entertainment and Design) talks in which knowledgable speakers address a variety of topics in short videos (< 18 minutes) 
[http://mathrun.net mathrun.net] - ''[Requires Flash]'' Practice your basic math skills with a simple game 
[http://justinguitar.com justinguitar.com] - Hundreds of free guitar lessons as well as some basic music theory. 
[http://duolingo.com duolingo.com] - Learn a new language for free while helping to translate the web! 
[http://memrise.com memrise.com] - ''[Requires Flash]'' Learn things quickly and efficiently with flashcards that are spaced based on the spacing effect 
[http://cookingforengineers.com cookingforengineers.com] - A site containing one man's explorations in food, with step by step instructions for making a wide variety of dishes. 
[http://mentalfloss.com mentalfloss.com] - Articles meant to expose you to interesting info, whether to "make you smile" or to really get you thinking. 
[http://openculture.com openculture.com] - Compendium of free learning resources, including courses, textbooks, and videos/films. 
[http://ocw.mit.edu ocw.mit.edu] - Free access to quite a few MIT courses that are on par with what you'd expect from MIT. 
[http://investopedia.com investopedia.com] - Learn about the world of finance, from basic terminology to in depth analysis of various areas of investing. 
[http://udacity.com udacity.com] - ''[Requires Flash]'' Free courses mainly focused around mathematics and programming. Aimed at people of all skill levels. 
[http://lang-8.com lang-8.com] - Write posts in a language you're trying to learn, get them critiqued by a native speaker (and in turn help that native speaker learn your language)! 
[http://engineerguy.com engineerguy.com] - ''[Requires Flash]'' Collection of videos in which Bill breaks down various feats of engineering in layman's terms. 
[http://zooniverse.org zooniverse.org] - Take part in investigating various interesting studies of nature, science, and culture. 
[http://aldaily.com aldaily.com] - Aggregation of articles from various higher education journals and publications. 
[http://livemocha.com livemocha.com] - ''[Requires Flash]'' Community dedicated to the idea of everyone being fluent in multiple languages, teach or be taught another language with the goal of conversational fluency. 
[http://simplesciencefitness.com simplesciencefitness.com] - Breaking down the science behind fitness into layman's terms. 
[http://edx.org edx.org] - EdX is a not-for-profit enterprise of its founding partners Harvard University and the Massachusetts Institute of Technology that features learning designed specifically for interactive study via the web. 
[http://learnerstv.com learnerstv.com] - ''[Requires Flash]'' Video lectures of many subjects: Math, Business, History, Philosophy and more. 
[http://academicearth.org academicearth.org] - ''[Requires Flash]'' Compilation of video lectures from different collegiate sources. 
[http://cnx.org/content cnx.org/content] - A huge database of content covering Arts, Business, Humanities, Math, Science and Social Sciences created by users, professors, and universities. 
[http://nature.com/scitable nature.com/scitable] - Learn biology and genetics through free ebooks and hundreds of articles covering several topics. 
[http://ureddit.com ureddit.com] - Classes taught by regular people with expertise in the field. Not accredited professors or lecturers, which may not necessarily be a bad thing. 
[http://uopeople.org uopeople.org] - ''[Requires Flash]'' Tuition free online university. 
[http://littlebridge.com littlebridge.com] - ''[Requires Flash]'' For kids; allows user to practice "talking" in English to other members. 
[http://rong-chang.com/kids.htm rong-chang.com/kids.htm] - ''[Requires Flash]'' For younger learners; has a variety of different levels for the learner. 
[http://mrnussbaum.com/lunchlady mrnussbaum.com/lunchlady] - ''[Requires Flash]'' Kid friendly; has lots of pictures and examples. 

http://www.starfall.com/ni/imglinks/everyday185x40a.gif 

[http://www.starfall.com Starfall.com] - ''[Requires Flash]'' - "A free public service to teach children to read with phonics. Our systematic phonics approach, in conjunction with phonemic awareness practice, is perfect for preschool, kindergarten, first grade, second grade, special education, homeschool, and English language development (ELD, ELL, ESL)." Superb for learning to read English!

Educational Tools

2013-12-09T19:20:34Z

David Kergyl: Added Starfall.

<h3>Hello! This is a list of some of the best educational tools/sites found on the internet. </h3>
(As recommended by community members -- this list is not endorsed by Sugar Labs)

Feel free to enjoy any and all of them, and please, if you know of any more sites that might be beneficial to add here, please add it! This is a community list.

[http://khanacademy.org khanacademy.org] - Watch thousands of micro-lectures on topics ranging from history and medicine to chemistry and computer science! 
[http://freerice.com freerice.com] - Help end world hunger by correctly answering multiple-choice quizzes on a wide variety of subjects! 
[http://unplugthetv.com unplugthetv.com] - ''[Requires Flash]'' Randomly selects an educational video to watch instead of useless drivel. 
[http://coursera.org coursera.org] - Educational site that works with universities to get their courses on the internet, free for you to use! 
[http://lizardpoint.com lizardpoint.com] - ''[Requires Flash]'' A collection of browser-based games and the like to improve knowledge of geography, math, and such. 
[http://ted.com ted.com] - ''[Requires Flash]'' Collection of TED (Technology, Entertainment and Design) talks in which knowledgable speakers address a variety of topics in short videos (< 18 minutes) 
[http://mathrun.net mathrun.net] - ''[Requires Flash]'' Practice your basic math skills with a simple game 
[http://justinguitar.com justinguitar.com] - Hundreds of free guitar lessons as well as some basic music theory. 
[http://duolingo.com duolingo.com] - Learn a new language for free while helping to translate the web! 
[http://memrise.com memrise.com] - ''[Requires Flash]'' Learn things quickly and efficiently with flashcards that are spaced based on the spacing effect 
[http://cookingforengineers.com cookingforengineers.com] - A site containing one man's explorations in food, with step by step instructions for making a wide variety of dishes. 
[http://mentalfloss.com mentalfloss.com] - Articles meant to expose you to interesting info, whether to "make you smile" or to really get you thinking. 
[http://openculture.com openculture.com] - Compendium of free learning resources, including courses, textbooks, and videos/films. 
[http://ocw.mit.edu ocw.mit.edu] - Free access to quite a few MIT courses that are on par with what you'd expect from MIT. 
[http://investopedia.com investopedia.com] - Learn about the world of finance, from basic terminology to in depth analysis of various areas of investing. 
[http://udacity.com udacity.com] - ''[Requires Flash]'' Free courses mainly focused around mathematics and programming. Aimed at people of all skill levels. 
[http://lang-8.com lang-8.com] - Write posts in a language you're trying to learn, get them critiqued by a native speaker (and in turn help that native speaker learn your language)! 
[http://engineerguy.com engineerguy.com] - ''[Requires Flash]'' Collection of videos in which Bill breaks down various feats of engineering in layman's terms. 
[http://zooniverse.org zooniverse.org] - Take part in investigating various interesting studies of nature, science, and culture. 
[http://aldaily.com aldaily.com] - Aggregation of articles from various higher education journals and publications. 
[http://livemocha.com livemocha.com] - ''[Requires Flash]'' Community dedicated to the idea of everyone being fluent in multiple languages, teach or be taught another language with the goal of conversational fluency. 
[http://simplesciencefitness.com simplesciencefitness.com] - Breaking down the science behind fitness into layman's terms. 
[http://edx.org edx.org] - EdX is a not-for-profit enterprise of its founding partners Harvard University and the Massachusetts Institute of Technology that features learning designed specifically for interactive study via the web. 
[http://learnerstv.com learnerstv.com] - ''[Requires Flash]'' Video lectures of many subjects: Math, Business, History, Philosophy and more. 
[http://academicearth.org academicearth.org] - ''[Requires Flash]'' Compilation of video lectures from different collegiate sources. 
[http://cnx.org/content cnx.org/content] - A huge database of content covering Arts, Business, Humanities, Math, Science and Social Sciences created by users, professors, and universities. 
[http://nature.com/scitable nature.com/scitable] - Learn biology and genetics through free ebooks and hundreds of articles covering several topics. 
[http://ureddit.com ureddit.com] - Classes taught by regular people with expertise in the field. Not accredited professors or lecturers, which may not necessarily be a bad thing. 
[http://uopeople.org uopeople.org] - ''[Requires Flash]'' Tuition free online university. 
[http://littlebridge.com littlebridge.com] - ''[Requires Flash]'' For kids; allows user to practice "talking" in English to other members. 
[http://rong-chang.com/kids.htm rong-chang.com/kids.htm] - ''[Requires Flash]'' For younger learners; has a variety of different levels for the learner. 
[http://mrnussbaum.com/lunchlady mrnussbaum.com/lunchlady] - ''[Requires Flash]'' Kid friendly; has lots of pictures and examples. 
[http://www.starfall.com Starfall.com] - ''[Requires Flash]'' "A free public service to teach children to read with phonics. Our systematic phonics approach, in conjunction with phonemic awareness practice, is perfect for preschool, kindergarten, first grade, second grade, special education, homeschool, and English language development (ELD, ELL, ESL)." Superb for learning to read English!

Sugar on a Stick/E-Books

2010-03-15T15:03:03Z

David Kergyl:

Links of sources of e-books for children

*[http://www.archive.org/details/iacl Internet Archive Children's Library] Good source of illustrated books in several formats. DejaVu format is recommended.

*[http://drscavanaugh.org/ebooks/libraries/childrens_collections.htm Drs. Cavanaugh list]

*[http://www.gutenberg.org/wiki/Category:Children%27s_Bookshelf Project Gutenberg Children's Bookshelf] Mostly plain text books which can be read with the Read Etexts activity.

*[http://www.snee.com/epubkidsbooks/ Snee] Selection from Project Gutenberg.

*[http://www.epubbooks.com/genres epubBooks]

*[http://manybooks.net/about/ Manybooks.net]

*[http://www.onlinecourses.org/2009/11/11/100-useful-links-for-ebook-lovers/ 100 Useful Links for eBook Lovers] (lots of free book sources, don't know how much children's material there is- sorry)

*[http://onlinedegreeprograms.org/blog/2009/100-free-audio-books-you-should-have-read-by-now/ 100 Free Audio Books You Should Have Read By Now] (more links that need sorting through for suitable material but there is a children's section further down the page – audio ogg format books will play in Browse and could help for folks with visual disabilities or with spoken language learning).
**Audio book: [http://www.gutenberg.org/files/23897/ogg/23897-06.ogg '''The Owl and the Pussycat by Edward Lear''']

*[http://www.loc.gov/rr/rarebook/digitalcoll/digitalcoll-children.html US Library of Congress Rare Book Children's Literature Collection] A small number of classic children's stories in online and PDF formats.

*[http://www.baen.com/library/ Baen Free Library] Current and classic science fiction books which can be read online using Browse or downloaded in RTF format and read with Read Etexts. Most of the titles are suitable for older children.

*[http://craphound.com/littlebrother/download/ Little Brother] An excellent young adult science fiction novel that can be downloaded for free. EPUB, Plain Text, PDF, and XO library bundle versions are available.

*[http://digital.library.upenn.edu/women/_collections/newbery/newbery.html Newbery Medal Winners by Women Authors] HTML with original illustrations.

*[http://feedbooks.com/type/Young%20Readers/books/top Feedbooks Young Readers category]

*[http://en.childrenslibrary.org/ International Children's Digital Library] Books in many languages for young readers to read online.

*[http://www.starfall.com/ Starfall] 75 FLASH reading/writing resources that are also useful for pre-kindergarten, kindergarten and second grade. Excellent learn-to-read site! Requires [[Adobe Flash]].

Sugar on a Stick/Hardware

2010-03-13T22:25:20Z

David Kergyl: /* Program Members */ Add my hardware profile for Dell/non-compressed SoaS.

{{TOCright}}
== A SoaS Hardware Effort ==

=== What's this about ===

This attempt has been started shortly after the SoaS beta release on April 22nd and is focussed on tracking hardware compatibility with newer SoaS versions. The overall goal of this effort is to gather information about issues with various hardware configurations using [[Sugar_on_a_Stick|SoaS]]. So if you just came across an issue or want to help us by providing your hardware specs, please follow these instructions.

=== What we're doing ===

We're using the [http://www.smolts.org Smolt] project to keep information about the various systems. Smolt is a hardware profiler and has been introduced with [http://fedoraproject.org/wiki/Releases/Smolt Fedora 7]. Since then, also openSUSE has joined the project.

Smolt basically helps you to submit your hardware information to a place, where people like us developers can check them out. Smolt development is hosted [https://fedorahosted.org/smolt/ here] and if you're worried about your privacy, you can have a look at Smolt's [https://fedorahosted.org/smolt/wiki/PrivacyPolicy privacy policy], too. Note that you can remove your hardware information at any time - instructions for this are also listed below!

== Next Steps ==

So. What's next? Here're the instructions:

# Boot into SoaS and start the Terminal Activity.
# Just call (as root): ''smoltSendProfile''
# It will ask you again if you're sure and will also give you a link to your profile and an admin password then. Please keep those!

Now that you've received the link to your hardware profile, please add it to the table below, as this will help us a lot to get an overview on which hardware SoaS is used on where issues occur. Note that with your admin password, you'll be also able to rate your experience with SoaS regarding the hardware support on your profile page. You can also provide it if you're filing a bug report on our [https://launchpad.net/soas bug tracker].

What if you want to remove your information?
:Just type in the terminal (again as root): ''smoltDeleteProfile''

* Consider also reporting observations of your testing here, [[Sugar on a Stick/Getting Involved/Testing]].

== Measuring Responsiveness ==

We are trying to get a handle on what hardware produces a snappy experience, and what produces a sluggish, but acceptable experience. For slow machines, we are curious whether they could be upgraded by adding memory (potentially scavenged from other donated computers) or add a USB 2.0 card (<$10). We are imagining getting a good number of donated, older computers, and we are thinking ahead about how to turn these into acceptable computers that kids could take home.

Please report boot-up speed and how long it takes to open common activities for the 2nd time. Some of them are slow on the first load. Turtle Art, Browse and Write are good ones to look at.

Running <code>dstat -at --output dstat.log</code> in a terminal can be helpful.

== Program Members ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
| '''name''' || '''smolt''' || '''notes'''
|-
| Sebastian Dziallas || http://www.smolts.org/client/show/pub_cf5334e9-3337-49cd-a7af-747b77bbdda1 ||
|-
| Tom Gilliard || http://www.smolts.org/client/show/pub_cf76bc48-7208-438b-a17a-6a6e94b8b230 ||
|-
| James Simmons || http://www.smolts.org/client/show/pub_9bd8878e-aefa-4304-ac55-c87738969fdd || used boot diskette, Browse wouldn't start.
|-
| Mathieu Bridon || http://www.smolts.org/client/show/pub_27aeaf15-0c96-45bf-b9db-01fe5772492c ||
|-
| Tom Gilliard || http://www.smolts.org/client/show/pub_ec31848d-9ef1-4d51-a7ce-17b7998113f2 ||no wireless
|-
| Luya Tshimbalanga || http://smolts.org/client/show/pub_922b7f43-db28-4c56-8107-c95516dc2c59 || Freeze when multiple activities are open, audio and video not working on Record and TamTam
|-
| Tom Gilliard ||http://www.smolts.org/client/show/pub_34858d7b-dda5-4fc0-bcca-57ade97d6048 ||Fedora 11 beta with Sugar Desktop wired
|-
| James Simmons || http://www.smolts.org/client/show/pub_3aab3f17-ab4f-4883-a152-de25125d86bc || used boot diskette, everything works, word highlighting on Read Etexts lags behind spoken words.
|-
| Eduardo NH Silva || http://www.smolts.org/client/show/pub_fe227e13-5847-494c-b96b-cfe2484aab90 || Acer Aspire 3003LMI, no wireless (besides, it needs a proprietary firmware)
|-
| Frederick Grose || http://www.smolts.org/client/show/pub_ae2467bf-9802-4dfe-9849-69922fd9082b || VirtualBox2.2.0 on Jackalope64 host
|-
| Tom Gilliard || http://www.smolts.org/client/show/pub_b69296a9-4326-465e-b3e2-99963dfe75c3 || Soas2-200905031329 Live USB Creator Dell 520n
|-
| Frederick Grose || http://www.smolts.org/client/show/pub_7618393d-bf0c-4227-901a-0bb3f5cfc982 || USB stick prepared with livecd-iso-to-disk.sh on SoaS running in VirtualBox2.2.0
|-
| Caroline Meeks Dell || http://www.smolts.org/client/show/pub_fa888e3a-3c29-44dc-b1cb-e28be354f9c5 ||
|-
| Walter Bender || http://www.smolts.org/client/show/pub_270553cf-91ed-495c-834c-521da796d345 || Magalâes Classmate: no sound
|-
| Frederick Grose || http://www.smolts.org/client/show/pub_ee2f82d0-f863-454f-9d72-b1ee60fb3c65 || USB stick prepared with LiveUSB-creator3.6.5 on Vista32
|-
| Elena Grandi || http://www.smolts.org/client/show/pub_a3bddcf4-644e-43dd-b0a1-b84b5c3b7201 || Soas2-200905031329.iso prepared with livecd-iso-to-disk.sh
|-
| Frederick Grose || http://www.smolts.org/client/show/pub_f2cf5101-8203-4941-be03-408deedd03e5 || soas-beta (0414) installed in VirtualBox2.2.2 disc on Win7-64 with onboard livecd-iso-to-disk
|-
| Tom Gilliard || http://www.smolts.org/client/show/pub_8b055063-0284-4dc3-99cc-ed3a3fb98e1a ||Fedora 11Preview Gnome with Sugar Desktop on Virtual box 2.2.2
|-
| Nicolas Thill || http://www.smolts.org/client/show/pub_3f863f30-dc41-4cc9-b236-8ab41295da00 || Lenovo X61 running SoaS release 1 (snapshot)
|-
| Dave Bauer || http://www.smolts.org/client/show/pub_56a19e3b-42b9-4e2e-9461-09e674f431e5 || Asus eeePC 901 SoaS 20090524 LiveUSB Creator from F11 Preview
|-
| Frederick Grose || http://www.smolts.org/client/show/pub_afb10e3a-749a-43c2-9679-067b9ac6ce50 || soas-strawberry-vdi in VBox2.2.4 on Vista32 host
|-
| Tom Gilliard || http://www.smolts.org/client/show/pub_21fbc300-c0d7-4fb0-8a20-100dde28eedc || sugarVM F11 Appliance on EeePC1000HE running Ubuntu9.04 and VMPlayer wireless
|-
| Frederick Grose || http://www.smolts.org/client/show/pub_93fa0384-4b43-42c5-aa14-45fa662e77c1 || soas-2-blueberry on USB stick
|- 
| Frederick Grose || http://www.smolts.org/client/show/pub_ecb85c75-cf2a-4417-bf8b-4d275170cdd7 || soas-2-blueberry on USB stick
|- 
| David Kergyl || http://www.smolts.org/client/show/pub_9ce13a7d-e35d-45e7-8f2b-34ebc63577c2 || Dell Latitude D630 Soas-2-blueberry on non-compressed 4GB USB stick
|- 
| <your name here> || <your smolt link here> || <your comments here>
|- 
|} 

== Upcoming Improvements ==

We're working on getting Smolt integrated in a Sugar Activity to ease the process of submitting the information.

Find help

2010-03-13T21:56:01Z

David Kergyl: /* on Sugar activities */ Formatting correction.

<noinclude>{{Translations | [[Sugar help|english]] | [[Sugar help/lang-pt|português]] | [[Sugar help/lang-es|español]] | }}
{{TOCright}}</noinclude>

==Finding answers to help==
For general help on Sugar or about Sugar Labs, please see also

'''→''' '''[[Getting Started | Getting started]]'''

'''→''' '''[[Sugar Labs/FAQ | Sugar Labs FAQ]]''' - a compilation of the team FAQs

'''→''' '''[[:Category:FAQ]]''' - an index to all FAQ pages ('''with links for new questions''')

'''→''' '''[[:Category:Help]]''' - pages tagged as 'Help'

'''→''' '''[[:Category:HowTo]]''' - pages tagged as 'HowTo'

'''→''' '''[[Sugar_Labs/Communication channels#Forums|Community Forums]]''' - on-line forums with lots of topics

'''→''' '''[[OLPC:Support FAQ|OLPC's Support FAQ]]''' - FAQs about the XO laptop, its version of Sugar, and Activities.
: Much information is applicable to the current version of Sugar (e.g., using Activities). See also [[#OLPC_Project_Help_and_Information|OLPC Project Help and Information]] below.

  '''Former sites'''—these have a short history of problems, but are no longer preferred by Sugar Labs.

:: http://getsatisfaction.com/sugarlabs & http://launchpad.net/soas

===The Sugar Learners' manual===
{| class="wikitable"
|-
| [http://flossmanuals.net/Sugar http://wiki.sugarlabs.org/images/4/40/Sugarlabs_mainpage_07.png]
|available as: [http://en.flossmanuals.net/Sugar HTML] or [{{FlossmanualPDF}} .pdf] 128 pages, 8.3 MBytes (for saving or printing).
|}
===Sugar [[Glossary|glossary]]===
: There is a [[Glossary|glossary with commonly used acronyms available here]].

{{:Tutorials}}

===[[The Undiscoverable]]===

: We have tried hard to make it easy for children to [[Discovery|discover]] what they can do with Sugar software without being told. But that isn't always possible. So we have a list of things that teachers should know about, and be able to demonstrate. If you find some feature of the software incomprehensible, please add it to the list, and we will see what we can do for you and everybody else who runs into the same problem. Sometimes the answer is a click of the mouse away, but not always. We are, after all, introducing children to all of human knowledge. They will inevitably need help with much of it. It took all of our ancestors many years to get this far, so it is alright if children spend a few years hitting the highlights, and getting help to do it.

----

===OLPC Project Help and Information===
: For general help and information about the OLPC Project, please see these links at the [[olpc:The OLPC Wiki|The OLPC Wiki]]:
: [[OLPC:Official OLPC FAQ | Official OLPC FAQ]], [[OLPC:Support FAQ|Support FAQ]], for questions about the XO laptop and its use, [[OLPC:Support|Support]], for more support mechanisms, [[OLPC::Category:OLPC FAQ|:Category:OLPC FAQ]], and [[OLPC:Ask OLPC a Question | Ask OLPC a Question]] (in roughly that order).
----
===[[Request_New_Features| Request new features]]===
: Please use our [[Request_New_Features|Request New Features page]].
: If you can't find your answer, please request one or ''supply one!'' below:

== Help Requests:==
:Click on an '''[edit]''' link next to a topic paragraph below to enter your request or an answer (you will see more instructions on the edit form). '''But first''', if possible, login or register on the wiki, leave an email address (secured by your login password), and then you can choose to 'Watch' any page on the wiki (such as this one) by clicking the 'Watch tab', and you will receive an email if the page changes. Plus, others can respond to you privately by using the 'E-mail this user' link in the sidebar of your user page.

:There are also links for new questions on the [[:Category:FAQ]] pages.
===on Usage ===
:First, see the help links above.

* 

* I would like to install [[olpc:Adobe Flash|Adobe Flash]] Player in order to access the learn-to-read website www.starfall.com with Browser. (i) Can the Sugar Browser run the Adobe Flash Player plug-in? (ii) If so, please modify the YUM instructions from Adobe (copied below) as needed for the Sugar environment. I'm a Windows user, so please include all necessary Terminal instructions (e.g., to change to the correct directory). Thanks in advance.
*: Installation instructions for the YUM repository definition
*:# Click the download link to begin installation. A dialog box will appear asking you where to save the file.
*:# Save the .rpm file to your desktop and wait for the file to download completely.
*:# In terminal, navigate to the desktop and type # rpm -Uvh <rpm_package_file>. Click Enter. (Note: This must be done as a root user).
*:# Once the installation is complete, in terminal, type # yum install flash-plugin. Click Enter. (Note: This must be done as a root user).
*:# To verify the plugin is installed in Mozilla, launch Mozilla and choose Help > About Plug-ins from the browser menu.
*:: (See http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-3.) - [[User:David Kergyl|David Kergyl]] 23:14, 10 March 2010 (UTC)

===on [[Wiki_Team/Resources | the Wiki]] ===
:First, see the [[Wiki Team/Resources]] page.

* 

===on Submitting a bug===
:Please report problems or bugs on '''[[Submit_Bugs/Problems| Submit Bugs/Problems page]]'''.

* 

===on Releases===
:First, see this page, [[{{Upcoming Stable Release}}/Roadmap]].

* 

===on Distributions===
:First, see the '''[[Downloads]]''' and '''[[Supported systems]]''' pages.

* 

* Live CD in Spanish
*:Purport: I see as one of the selling points of Sugar that a non-expert user can use computers "off the bat". It has been reported to me that currently the LiveCD requires some tweaking at startup to adjust it to a given locale, which I feel is to ask too much precisely from users that are not skilled. Goal: a LiveCD version that is localized in Spanish from startup, with no tweaking required, to be distributable among the Spanish-speaking public.
*::Contact: yamaplos at bolinux.org

=== on Sugar hardware ports===
:First, see the '''[[Supported systems]]''' page.

* 

=== on Sugar activities===
:First, see the [[Activity Team]] pages.

* 

* According to this review, [[olpc:Scratch|Scratch]] requires some setup in Terminal:
*: ... Scratch lacks Sugar integration but it does have the benefit that you can store and retrieve Scratch in file folders which the user can setup. Unfortunately this does require some help with setting up files under Linux and giving the user write permission on those files. The plus side of all of this is that the user can read and write to a USB memory stick and share Scratch files with Scratch on other computers.... Rated 4 out of 5 stars by Bill on February 28, 2010
*:: Is this correct? Is such setup also required to use the Scratch included on the Blueberry SoaS? If so, please add a wiki section containing specific instructions for performing this setup in Terminal. The Scratch activities page should also link to the instructions. - [[User:David Kergyl|David Kergyl]] 16:36, 11 March 2010 (UTC)
*::: '''Thank you''' David for you contributions to the wiki both here and elsewhere! While you have entered your questions at appropriate places in the wiki for their future reference, if you accompany your question with a post to either of these [[Sugar Labs/Communication channels#Mailing Lists|mailing lists]], [http://lists.sugarlabs.org/listinfo/iaep It's An Education Project, IAEP] (for general), or [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] (for development-related) discussions, you will reach many more Sugar Labs followers who are not currently following changes on this wiki. We can then reference the discussion thread in the wiki and also provide a consolidated summary. --[[User:FGrose|FGrose]] 17:25, 11 March 2010 (UTC)

* Please add a Scratch activity page on the Sugar Labs wiki, with a link to [[olpc:Scratch|Scratch]]. --[[User:David Kergyl|David Kergyl]] 21:55, 13 March 2010 (UTC)

=== on Sugar deployments===
:First, see the [[Deployment Team]] pages.

* 

=== on Sugar Labs===
: See the '''[[Sugar Labs]]''' page. Sugar Labs was created to provide a mechanism for supporting the Sugar community of volunteers. These volunteers are engaged in a variety of activities: some are writing software to improve Sugar; some are porting Sugar to new platforms; some are developing new activities that run in Sugar; some are helping to debug Sugar and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios for learning with Sugar; some are using Sugar and reporting upon their experiences to the community; and some are providing help and support.

:Since we started Sugar Labs, we have been receiving a number of requests for help: porting Sugar to new distributions; tuning Sugar on a specific hardware platform; developing specific Sugar activity; helping with support in specific deployments, etc. Please use this page both to make requests and respond to requests for help.

* 

[[Category:General public]]
[[Category:Help]]

Find help

2010-03-13T21:55:27Z

David Kergyl: /* on Sugar activities */ Add request for Scratch activiy wiki page.

<noinclude>{{Translations | [[Sugar help|english]] | [[Sugar help/lang-pt|português]] | [[Sugar help/lang-es|español]] | }}
{{TOCright}}</noinclude>

==Finding answers to help==
For general help on Sugar or about Sugar Labs, please see also

'''→''' '''[[Getting Started | Getting started]]'''

'''→''' '''[[Sugar Labs/FAQ | Sugar Labs FAQ]]''' - a compilation of the team FAQs

'''→''' '''[[:Category:FAQ]]''' - an index to all FAQ pages ('''with links for new questions''')

'''→''' '''[[:Category:Help]]''' - pages tagged as 'Help'

'''→''' '''[[:Category:HowTo]]''' - pages tagged as 'HowTo'

'''→''' '''[[Sugar_Labs/Communication channels#Forums|Community Forums]]''' - on-line forums with lots of topics

'''→''' '''[[OLPC:Support FAQ|OLPC's Support FAQ]]''' - FAQs about the XO laptop, its version of Sugar, and Activities.
: Much information is applicable to the current version of Sugar (e.g., using Activities). See also [[#OLPC_Project_Help_and_Information|OLPC Project Help and Information]] below.

  '''Former sites'''—these have a short history of problems, but are no longer preferred by Sugar Labs.

:: http://getsatisfaction.com/sugarlabs & http://launchpad.net/soas

===The Sugar Learners' manual===
{| class="wikitable"
|-
| [http://flossmanuals.net/Sugar http://wiki.sugarlabs.org/images/4/40/Sugarlabs_mainpage_07.png]
|available as: [http://en.flossmanuals.net/Sugar HTML] or [{{FlossmanualPDF}} .pdf] 128 pages, 8.3 MBytes (for saving or printing).
|}
===Sugar [[Glossary|glossary]]===
: There is a [[Glossary|glossary with commonly used acronyms available here]].

{{:Tutorials}}

===[[The Undiscoverable]]===

: We have tried hard to make it easy for children to [[Discovery|discover]] what they can do with Sugar software without being told. But that isn't always possible. So we have a list of things that teachers should know about, and be able to demonstrate. If you find some feature of the software incomprehensible, please add it to the list, and we will see what we can do for you and everybody else who runs into the same problem. Sometimes the answer is a click of the mouse away, but not always. We are, after all, introducing children to all of human knowledge. They will inevitably need help with much of it. It took all of our ancestors many years to get this far, so it is alright if children spend a few years hitting the highlights, and getting help to do it.

----

===OLPC Project Help and Information===
: For general help and information about the OLPC Project, please see these links at the [[olpc:The OLPC Wiki|The OLPC Wiki]]:
: [[OLPC:Official OLPC FAQ | Official OLPC FAQ]], [[OLPC:Support FAQ|Support FAQ]], for questions about the XO laptop and its use, [[OLPC:Support|Support]], for more support mechanisms, [[OLPC::Category:OLPC FAQ|:Category:OLPC FAQ]], and [[OLPC:Ask OLPC a Question | Ask OLPC a Question]] (in roughly that order).
----
===[[Request_New_Features| Request new features]]===
: Please use our [[Request_New_Features|Request New Features page]].
: If you can't find your answer, please request one or ''supply one!'' below:

== Help Requests:==
:Click on an '''[edit]''' link next to a topic paragraph below to enter your request or an answer (you will see more instructions on the edit form). '''But first''', if possible, login or register on the wiki, leave an email address (secured by your login password), and then you can choose to 'Watch' any page on the wiki (such as this one) by clicking the 'Watch tab', and you will receive an email if the page changes. Plus, others can respond to you privately by using the 'E-mail this user' link in the sidebar of your user page.

:There are also links for new questions on the [[:Category:FAQ]] pages.
===on Usage ===
:First, see the help links above.

* 

* I would like to install [[olpc:Adobe Flash|Adobe Flash]] Player in order to access the learn-to-read website www.starfall.com with Browser. (i) Can the Sugar Browser run the Adobe Flash Player plug-in? (ii) If so, please modify the YUM instructions from Adobe (copied below) as needed for the Sugar environment. I'm a Windows user, so please include all necessary Terminal instructions (e.g., to change to the correct directory). Thanks in advance.
*: Installation instructions for the YUM repository definition
*:# Click the download link to begin installation. A dialog box will appear asking you where to save the file.
*:# Save the .rpm file to your desktop and wait for the file to download completely.
*:# In terminal, navigate to the desktop and type # rpm -Uvh <rpm_package_file>. Click Enter. (Note: This must be done as a root user).
*:# Once the installation is complete, in terminal, type # yum install flash-plugin. Click Enter. (Note: This must be done as a root user).
*:# To verify the plugin is installed in Mozilla, launch Mozilla and choose Help > About Plug-ins from the browser menu.
*:: (See http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-3.) - [[User:David Kergyl|David Kergyl]] 23:14, 10 March 2010 (UTC)

===on [[Wiki_Team/Resources | the Wiki]] ===
:First, see the [[Wiki Team/Resources]] page.

* 

===on Submitting a bug===
:Please report problems or bugs on '''[[Submit_Bugs/Problems| Submit Bugs/Problems page]]'''.

* 

===on Releases===
:First, see this page, [[{{Upcoming Stable Release}}/Roadmap]].

* 

===on Distributions===
:First, see the '''[[Downloads]]''' and '''[[Supported systems]]''' pages.

* 

* Live CD in Spanish
*:Purport: I see as one of the selling points of Sugar that a non-expert user can use computers "off the bat". It has been reported to me that currently the LiveCD requires some tweaking at startup to adjust it to a given locale, which I feel is to ask too much precisely from users that are not skilled. Goal: a LiveCD version that is localized in Spanish from startup, with no tweaking required, to be distributable among the Spanish-speaking public.
*::Contact: yamaplos at bolinux.org

=== on Sugar hardware ports===
:First, see the '''[[Supported systems]]''' page.

* 

=== on Sugar activities===
:First, see the [[Activity Team]] pages.

* 

* According to this review, [[olpc:Scratch|Scratch]] requires some setup in Terminal:
*: ... Scratch lacks Sugar integration but it does have the benefit that you can store and retrieve Scratch in file folders which the user can setup. Unfortunately this does require some help with setting up files under Linux and giving the user write permission on those files. The plus side of all of this is that the user can read and write to a USB memory stick and share Scratch files with Scratch on other computers.... Rated 4 out of 5 stars by Bill on February 28, 2010
*:: Is this correct? Is such setup also required to use the Scratch included on the Blueberry SoaS? If so, please add a wiki section containing specific instructions for performing this setup in Terminal. The Scratch activities page should also link to the instructions. - [[User:David Kergyl|David Kergyl]] 16:36, 11 March 2010 (UTC)
*::: '''Thank you''' David for you contributions to the wiki both here and elsewhere! While you have entered your questions at appropriate places in the wiki for their future reference, if you accompany your question with a post to either of these [[Sugar Labs/Communication channels#Mailing Lists|mailing lists]], [http://lists.sugarlabs.org/listinfo/iaep It's An Education Project, IAEP] (for general), or [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] (for development-related) discussions, you will reach many more Sugar Labs followers who are not currently following changes on this wiki. We can then reference the discussion thread in the wiki and also provide a consolidated summary. --[[User:FGrose|FGrose]] 17:25, 11 March 2010 (UTC)

* Please add a Scratch activity page on the Sugar Labs wiki, with a link to [[[[olpc:Scratch|Scratch]]. --[[User:David Kergyl|David Kergyl]] 21:55, 13 March 2010 (UTC)

=== on Sugar deployments===
:First, see the [[Deployment Team]] pages.

* 

=== on Sugar Labs===
: See the '''[[Sugar Labs]]''' page. Sugar Labs was created to provide a mechanism for supporting the Sugar community of volunteers. These volunteers are engaged in a variety of activities: some are writing software to improve Sugar; some are porting Sugar to new platforms; some are developing new activities that run in Sugar; some are helping to debug Sugar and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios for learning with Sugar; some are using Sugar and reporting upon their experiences to the community; and some are providing help and support.

:Since we started Sugar Labs, we have been receiving a number of requests for help: porting Sugar to new distributions; tuning Sugar on a specific hardware platform; developing specific Sugar activity; helping with support in specific deployments, etc. Please use this page both to make requests and respond to requests for help.

* 

[[Category:General public]]
[[Category:Help]]

Submit Bugs/Problems

2010-03-13T20:55:53Z

David Kergyl: /* Please Describe Bugs & Problems Here */ Add upload log files . . .

<noinclude>{{TOCright}}</noinclude>

== Please Describe Bugs & Problems Here ==
* Communicate directly with the [[Development Team]]'s work ticket system by using the [http://bugs.sugarlabs.org Sugar Labs '''trac''' instance] to report bugs you find with Sugar on the various distributions.
* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.
* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.
* In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem. You may also [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Getting_Involved/Testing#Report_your_hardware_profile report your hardware profile] and upload log files as described in [[OLPC:Reporting bugs]].
* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.

Email sent to feedback AT sugarlabs.org will be forwarded to the IAEP mailing list, which is used for general discussion of the Sugar Labs education project.

===Journal comes and goes===
Sugar on Ubuntu doesn't always preserve the Journal between sessions.
:It seems that the index is occasionally broken and the datastore is thus copied to a timestamped entry in .sugar/default/ and empty datastore is opened.
::Is this still a problem with 0.84? If so, could you [http://trac.sugarlabs.org please file a ticket]?

===.84 sugar===
Apps won't load in Fedora 11 emulating sugar under root.
Video of behavior: http://www.youtube.com/watch?v=1Lvvjvi3yE0
===Colors on Ubuntu===
The Colors activity canvas is only half the width of the screen and the aspect ratio is compressed.
:This bug is being tracked in [http://trac.sugarlabs.org/ticket/592 Ticket 592]

===Turtle Art===
Turtle Art on a non-1200x900 screen doesn't scale display.
:Resolved since Version 17.

===Hover menus from the Frame on Ubuntu===
They appear in the upper-left corner.
:Resolved in 0.84

===Can't Shutdown Sugar Spin===
I am using the Sugar Spin on a CD and nothing happens when I click on shutdown.
:The Sugar LiveCD and LiveUSB releases are going through a lot of testing and newer versions are more reliable. Please try again at [[Downloads]].

===WPA/WEP Connectivity Problems===

Hi I still have problems connecting to WPA, even with build 703 installed. I enter a password and nothing happens. Any advice?
:Hmmm. This one falls between the crack of Sugar and the OLPC network stack. Have you asked for help from the OLPC support team? --[[User:Walter|Walter]] 19:57, 22 May 2008 (UTC)
::Looks like a place where more feedback should be given in the UI. Any concrete ideas? [[User:Tomeu|Tomeu]] 09:31, 23 May 2008 (UTC)

No, I haven't. Maybe we should explain what questions should go to OLPC team and what goes here.
:Good point. --[[User:Walter|Walter]] 20:15, 22 May 2008 (UTC)

===UI Element sizes===
This is more of an issue than a bug. But I don't know where else to put it for now.

As Sugar is ported to other systems, they will have screens with dimensions significantly different than the XO laptop. On the XO the assumption is made of 1200 x 900 pix, with Sugar occupying a grid of 12 x 16 elements 75 pixels square.

How will we deal with issues like screens in other aspect ratios, or where the 75-pixel element is not a practical size?
[[User:Rmyers|Rmyers]] 20:51, 22 May 2008 (UTC)

:Much of this is ameliorated by the extensive use of SVG for the graphics. --[[User:Walter|Walter]] 21:10, 22 May 2008 (UTC)
:There is active development on this issue. See, for example, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg02712.html. --[[User:FGrose|FGrose]] 04:56, 20 March 2009 (UTC)

===Sonata===

I cannot access MP3 files I transfer to my SD card through Sonata. It does not let me select source directories/devices. Any advice? Is there a better player for Sugar/XO?
:perhaps you'll have better luck with [http://activities.sugarlabs.org/en-US/sugar/addon/4045 Jukebox]? If not, please [http://dev.sugarlabs.org file a bug report]

[[Category:General public]]

===Login fail on Fedora 9===

I have sugar installed on Fedora 9. The first session I start allows me to give my name and choose my colour. After that the session aborts with no further communication. Every subsequent session aborts with no error message. The only useful looking message is in the .xsession-errors file and looks like this.

*** PULSEAUDIO: Unable to connect: Connection refused
*** Is your sound server running?
*** See: http://www.pulseaudio.org/wiki/Troubleshooting

** (sugar-shell:12977): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion `GST_IS_MIXER (self->obj)' failed

I checked over the fedora bug tracker and found some missing dependencies mentioned, but those were all installed (e.g. gstreamer). When doing this I was using a second X session to my main one, but previously I have had the same problem in the main X session. Any suggestions?

:I'll see if someone from the Fedora team can offer some help. --[[User:Walter|Walter]] 22:49, 21 September 2008 (UTC)
::What I have learned so far (from Marco)
::The Fedora 9 packages are basically untested :( Rawhide is getting much better. Perhaps we should spend a bit of time one of these days and push the latest packages in Fedora 9.
::There is a sugar component on http://bugzilla.redhat.com which can be used for distribution specific issues. Upstream issues should be reported to dev.laptop.org. Yeah, it can be hard/impossible for the user to know if it's distribution or upstream. I suggest to always give priority to upstream when unsure. --[[User:Walter|Walter]] 12:57, 22 September 2008 (UTC)
::This resolved in the F11 release. --[[User:Walter|Walter]] 13:54, 20 March 2009 (UTC)

===XOlympics activity fails if python-elements package installed on Fedora 12===

XOlympics uses a custom local "elements" module, but if python-elements is installed, XOlympics can't find box2d because it looks it finds the site-wide elements module first. The Physics activity seems to require that python-elements is installed, so the only workaround I found was to add:

import sys
sys.path.insert(0, ".")

to the top of "XOlympics.activity/tools.py"

--[[User:DeanBrettle|DeanBrettle]] 13:12, 6 February 2010

Submit Bugs/Problems

2010-03-13T20:00:31Z

David Kergyl: /* Please Describe Bugs & Problems Here */ Tighten language.

<noinclude>{{TOCright}}</noinclude>

== Please Describe Bugs & Problems Here ==
* Communicate directly with the [[Development Team]]'s work ticket system by using the [http://bugs.sugarlabs.org Sugar Labs '''trac''' instance] to report bugs you find with Sugar on the various distributions.
* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.
* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.
* In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem. You may also [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Getting_Involved/Testing#Report_your_hardware_profile report your hardware profile].
* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.

Email sent to feedback AT sugarlabs.org will be forwarded to the IAEP mailing list, which is used for general discussion of the Sugar Labs education project.

===Journal comes and goes===
Sugar on Ubuntu doesn't always preserve the Journal between sessions.
:It seems that the index is occasionally broken and the datastore is thus copied to a timestamped entry in .sugar/default/ and empty datastore is opened.
::Is this still a problem with 0.84? If so, could you [http://trac.sugarlabs.org please file a ticket]?

===.84 sugar===
Apps won't load in Fedora 11 emulating sugar under root.
Video of behavior: http://www.youtube.com/watch?v=1Lvvjvi3yE0
===Colors on Ubuntu===
The Colors activity canvas is only half the width of the screen and the aspect ratio is compressed.
:This bug is being tracked in [http://trac.sugarlabs.org/ticket/592 Ticket 592]

===Turtle Art===
Turtle Art on a non-1200x900 screen doesn't scale display.
:Resolved since Version 17.

===Hover menus from the Frame on Ubuntu===
They appear in the upper-left corner.
:Resolved in 0.84

===Can't Shutdown Sugar Spin===
I am using the Sugar Spin on a CD and nothing happens when I click on shutdown.
:The Sugar LiveCD and LiveUSB releases are going through a lot of testing and newer versions are more reliable. Please try again at [[Downloads]].

===WPA/WEP Connectivity Problems===

Hi I still have problems connecting to WPA, even with build 703 installed. I enter a password and nothing happens. Any advice?
:Hmmm. This one falls between the crack of Sugar and the OLPC network stack. Have you asked for help from the OLPC support team? --[[User:Walter|Walter]] 19:57, 22 May 2008 (UTC)
::Looks like a place where more feedback should be given in the UI. Any concrete ideas? [[User:Tomeu|Tomeu]] 09:31, 23 May 2008 (UTC)

No, I haven't. Maybe we should explain what questions should go to OLPC team and what goes here.
:Good point. --[[User:Walter|Walter]] 20:15, 22 May 2008 (UTC)

===UI Element sizes===
This is more of an issue than a bug. But I don't know where else to put it for now.

As Sugar is ported to other systems, they will have screens with dimensions significantly different than the XO laptop. On the XO the assumption is made of 1200 x 900 pix, with Sugar occupying a grid of 12 x 16 elements 75 pixels square.

How will we deal with issues like screens in other aspect ratios, or where the 75-pixel element is not a practical size?
[[User:Rmyers|Rmyers]] 20:51, 22 May 2008 (UTC)

:Much of this is ameliorated by the extensive use of SVG for the graphics. --[[User:Walter|Walter]] 21:10, 22 May 2008 (UTC)
:There is active development on this issue. See, for example, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg02712.html. --[[User:FGrose|FGrose]] 04:56, 20 March 2009 (UTC)

===Sonata===

I cannot access MP3 files I transfer to my SD card through Sonata. It does not let me select source directories/devices. Any advice? Is there a better player for Sugar/XO?
:perhaps you'll have better luck with [http://activities.sugarlabs.org/en-US/sugar/addon/4045 Jukebox]? If not, please [http://dev.sugarlabs.org file a bug report]

[[Category:General public]]

===Login fail on Fedora 9===

I have sugar installed on Fedora 9. The first session I start allows me to give my name and choose my colour. After that the session aborts with no further communication. Every subsequent session aborts with no error message. The only useful looking message is in the .xsession-errors file and looks like this.

*** PULSEAUDIO: Unable to connect: Connection refused
*** Is your sound server running?
*** See: http://www.pulseaudio.org/wiki/Troubleshooting

** (sugar-shell:12977): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion `GST_IS_MIXER (self->obj)' failed

I checked over the fedora bug tracker and found some missing dependencies mentioned, but those were all installed (e.g. gstreamer). When doing this I was using a second X session to my main one, but previously I have had the same problem in the main X session. Any suggestions?

:I'll see if someone from the Fedora team can offer some help. --[[User:Walter|Walter]] 22:49, 21 September 2008 (UTC)
::What I have learned so far (from Marco)
::The Fedora 9 packages are basically untested :( Rawhide is getting much better. Perhaps we should spend a bit of time one of these days and push the latest packages in Fedora 9.
::There is a sugar component on http://bugzilla.redhat.com which can be used for distribution specific issues. Upstream issues should be reported to dev.laptop.org. Yeah, it can be hard/impossible for the user to know if it's distribution or upstream. I suggest to always give priority to upstream when unsure. --[[User:Walter|Walter]] 12:57, 22 September 2008 (UTC)
::This resolved in the F11 release. --[[User:Walter|Walter]] 13:54, 20 March 2009 (UTC)

===XOlympics activity fails if python-elements package installed on Fedora 12===

XOlympics uses a custom local "elements" module, but if python-elements is installed, XOlympics can't find box2d because it looks it finds the site-wide elements module first. The Physics activity seems to require that python-elements is installed, so the only workaround I found was to add:

import sys
sys.path.insert(0, ".")

to the top of "XOlympics.activity/tools.py"

--[[User:DeanBrettle|DeanBrettle]] 13:12, 6 February 2010

Submit Bugs/Problems

2010-03-13T19:57:00Z

David Kergyl: /* Please Describe Bugs & Problems Here */ Correct link to report hardware profile.

<noinclude>{{TOCright}}</noinclude>

== Please Describe Bugs & Problems Here ==
* Communicate directly with the [[Development Team]]'s work ticket system by using the [http://bugs.sugarlabs.org Sugar Labs '''trac''' instance] to report bugs you find with Sugar on the various distributions.
* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.
* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.
* In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem. You may also want to [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Getting_Involved/Testing#Report_your_hardware_profile report your hardware profile].
* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.

Email sent to feedback AT sugarlabs.org will be forwarded to the IAEP mailing list, which is used for general discussion of the Sugar Labs education project.

===Journal comes and goes===
Sugar on Ubuntu doesn't always preserve the Journal between sessions.
:It seems that the index is occasionally broken and the datastore is thus copied to a timestamped entry in .sugar/default/ and empty datastore is opened.
::Is this still a problem with 0.84? If so, could you [http://trac.sugarlabs.org please file a ticket]?

===.84 sugar===
Apps won't load in Fedora 11 emulating sugar under root.
Video of behavior: http://www.youtube.com/watch?v=1Lvvjvi3yE0
===Colors on Ubuntu===
The Colors activity canvas is only half the width of the screen and the aspect ratio is compressed.
:This bug is being tracked in [http://trac.sugarlabs.org/ticket/592 Ticket 592]

===Turtle Art===
Turtle Art on a non-1200x900 screen doesn't scale display.
:Resolved since Version 17.

===Hover menus from the Frame on Ubuntu===
They appear in the upper-left corner.
:Resolved in 0.84

===Can't Shutdown Sugar Spin===
I am using the Sugar Spin on a CD and nothing happens when I click on shutdown.
:The Sugar LiveCD and LiveUSB releases are going through a lot of testing and newer versions are more reliable. Please try again at [[Downloads]].

===WPA/WEP Connectivity Problems===

Hi I still have problems connecting to WPA, even with build 703 installed. I enter a password and nothing happens. Any advice?
:Hmmm. This one falls between the crack of Sugar and the OLPC network stack. Have you asked for help from the OLPC support team? --[[User:Walter|Walter]] 19:57, 22 May 2008 (UTC)
::Looks like a place where more feedback should be given in the UI. Any concrete ideas? [[User:Tomeu|Tomeu]] 09:31, 23 May 2008 (UTC)

No, I haven't. Maybe we should explain what questions should go to OLPC team and what goes here.
:Good point. --[[User:Walter|Walter]] 20:15, 22 May 2008 (UTC)

===UI Element sizes===
This is more of an issue than a bug. But I don't know where else to put it for now.

As Sugar is ported to other systems, they will have screens with dimensions significantly different than the XO laptop. On the XO the assumption is made of 1200 x 900 pix, with Sugar occupying a grid of 12 x 16 elements 75 pixels square.

How will we deal with issues like screens in other aspect ratios, or where the 75-pixel element is not a practical size?
[[User:Rmyers|Rmyers]] 20:51, 22 May 2008 (UTC)

:Much of this is ameliorated by the extensive use of SVG for the graphics. --[[User:Walter|Walter]] 21:10, 22 May 2008 (UTC)
:There is active development on this issue. See, for example, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg02712.html. --[[User:FGrose|FGrose]] 04:56, 20 March 2009 (UTC)

===Sonata===

I cannot access MP3 files I transfer to my SD card through Sonata. It does not let me select source directories/devices. Any advice? Is there a better player for Sugar/XO?
:perhaps you'll have better luck with [http://activities.sugarlabs.org/en-US/sugar/addon/4045 Jukebox]? If not, please [http://dev.sugarlabs.org file a bug report]

[[Category:General public]]

===Login fail on Fedora 9===

I have sugar installed on Fedora 9. The first session I start allows me to give my name and choose my colour. After that the session aborts with no further communication. Every subsequent session aborts with no error message. The only useful looking message is in the .xsession-errors file and looks like this.

*** PULSEAUDIO: Unable to connect: Connection refused
*** Is your sound server running?
*** See: http://www.pulseaudio.org/wiki/Troubleshooting

** (sugar-shell:12977): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion `GST_IS_MIXER (self->obj)' failed

I checked over the fedora bug tracker and found some missing dependencies mentioned, but those were all installed (e.g. gstreamer). When doing this I was using a second X session to my main one, but previously I have had the same problem in the main X session. Any suggestions?

:I'll see if someone from the Fedora team can offer some help. --[[User:Walter|Walter]] 22:49, 21 September 2008 (UTC)
::What I have learned so far (from Marco)
::The Fedora 9 packages are basically untested :( Rawhide is getting much better. Perhaps we should spend a bit of time one of these days and push the latest packages in Fedora 9.
::There is a sugar component on http://bugzilla.redhat.com which can be used for distribution specific issues. Upstream issues should be reported to dev.laptop.org. Yeah, it can be hard/impossible for the user to know if it's distribution or upstream. I suggest to always give priority to upstream when unsure. --[[User:Walter|Walter]] 12:57, 22 September 2008 (UTC)
::This resolved in the F11 release. --[[User:Walter|Walter]] 13:54, 20 March 2009 (UTC)

===XOlympics activity fails if python-elements package installed on Fedora 12===

XOlympics uses a custom local "elements" module, but if python-elements is installed, XOlympics can't find box2d because it looks it finds the site-wide elements module first. The Physics activity seems to require that python-elements is installed, so the only workaround I found was to add:

import sys
sys.path.insert(0, ".")

to the top of "XOlympics.activity/tools.py"

--[[User:DeanBrettle|DeanBrettle]] 13:12, 6 February 2010

Submit Bugs/Problems

2010-03-13T19:56:13Z

David Kergyl: /* Please Describe Bugs & Problems Here */ Add link to report hardware profile.

<noinclude>{{TOCright}}</noinclude>

== Please Describe Bugs & Problems Here ==
* Communicate directly with the [[Development Team]]'s work ticket system by using the [http://bugs.sugarlabs.org Sugar Labs '''trac''' instance] to report bugs you find with Sugar on the various distributions.
* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.
* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.
* In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem. You may also want to [[Report your hardware profile]].
* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.

Email sent to feedback AT sugarlabs.org will be forwarded to the IAEP mailing list, which is used for general discussion of the Sugar Labs education project.

===Journal comes and goes===
Sugar on Ubuntu doesn't always preserve the Journal between sessions.
:It seems that the index is occasionally broken and the datastore is thus copied to a timestamped entry in .sugar/default/ and empty datastore is opened.
::Is this still a problem with 0.84? If so, could you [http://trac.sugarlabs.org please file a ticket]?

===.84 sugar===
Apps won't load in Fedora 11 emulating sugar under root.
Video of behavior: http://www.youtube.com/watch?v=1Lvvjvi3yE0
===Colors on Ubuntu===
The Colors activity canvas is only half the width of the screen and the aspect ratio is compressed.
:This bug is being tracked in [http://trac.sugarlabs.org/ticket/592 Ticket 592]

===Turtle Art===
Turtle Art on a non-1200x900 screen doesn't scale display.
:Resolved since Version 17.

===Hover menus from the Frame on Ubuntu===
They appear in the upper-left corner.
:Resolved in 0.84

===Can't Shutdown Sugar Spin===
I am using the Sugar Spin on a CD and nothing happens when I click on shutdown.
:The Sugar LiveCD and LiveUSB releases are going through a lot of testing and newer versions are more reliable. Please try again at [[Downloads]].

===WPA/WEP Connectivity Problems===

Hi I still have problems connecting to WPA, even with build 703 installed. I enter a password and nothing happens. Any advice?
:Hmmm. This one falls between the crack of Sugar and the OLPC network stack. Have you asked for help from the OLPC support team? --[[User:Walter|Walter]] 19:57, 22 May 2008 (UTC)
::Looks like a place where more feedback should be given in the UI. Any concrete ideas? [[User:Tomeu|Tomeu]] 09:31, 23 May 2008 (UTC)

No, I haven't. Maybe we should explain what questions should go to OLPC team and what goes here.
:Good point. --[[User:Walter|Walter]] 20:15, 22 May 2008 (UTC)

===UI Element sizes===
This is more of an issue than a bug. But I don't know where else to put it for now.

As Sugar is ported to other systems, they will have screens with dimensions significantly different than the XO laptop. On the XO the assumption is made of 1200 x 900 pix, with Sugar occupying a grid of 12 x 16 elements 75 pixels square.

How will we deal with issues like screens in other aspect ratios, or where the 75-pixel element is not a practical size?
[[User:Rmyers|Rmyers]] 20:51, 22 May 2008 (UTC)

:Much of this is ameliorated by the extensive use of SVG for the graphics. --[[User:Walter|Walter]] 21:10, 22 May 2008 (UTC)
:There is active development on this issue. See, for example, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg02712.html. --[[User:FGrose|FGrose]] 04:56, 20 March 2009 (UTC)

===Sonata===

I cannot access MP3 files I transfer to my SD card through Sonata. It does not let me select source directories/devices. Any advice? Is there a better player for Sugar/XO?
:perhaps you'll have better luck with [http://activities.sugarlabs.org/en-US/sugar/addon/4045 Jukebox]? If not, please [http://dev.sugarlabs.org file a bug report]

[[Category:General public]]

===Login fail on Fedora 9===

I have sugar installed on Fedora 9. The first session I start allows me to give my name and choose my colour. After that the session aborts with no further communication. Every subsequent session aborts with no error message. The only useful looking message is in the .xsession-errors file and looks like this.

*** PULSEAUDIO: Unable to connect: Connection refused
*** Is your sound server running?
*** See: http://www.pulseaudio.org/wiki/Troubleshooting

** (sugar-shell:12977): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion `GST_IS_MIXER (self->obj)' failed

I checked over the fedora bug tracker and found some missing dependencies mentioned, but those were all installed (e.g. gstreamer). When doing this I was using a second X session to my main one, but previously I have had the same problem in the main X session. Any suggestions?

:I'll see if someone from the Fedora team can offer some help. --[[User:Walter|Walter]] 22:49, 21 September 2008 (UTC)
::What I have learned so far (from Marco)
::The Fedora 9 packages are basically untested :( Rawhide is getting much better. Perhaps we should spend a bit of time one of these days and push the latest packages in Fedora 9.
::There is a sugar component on http://bugzilla.redhat.com which can be used for distribution specific issues. Upstream issues should be reported to dev.laptop.org. Yeah, it can be hard/impossible for the user to know if it's distribution or upstream. I suggest to always give priority to upstream when unsure. --[[User:Walter|Walter]] 12:57, 22 September 2008 (UTC)
::This resolved in the F11 release. --[[User:Walter|Walter]] 13:54, 20 March 2009 (UTC)

===XOlympics activity fails if python-elements package installed on Fedora 12===

XOlympics uses a custom local "elements" module, but if python-elements is installed, XOlympics can't find box2d because it looks it finds the site-wide elements module first. The Physics activity seems to require that python-elements is installed, so the only workaround I found was to add:

import sys
sys.path.insert(0, ".")

to the top of "XOlympics.activity/tools.py"

--[[User:DeanBrettle|DeanBrettle]] 13:12, 6 February 2010

User talk:FGrose

2010-03-13T19:28:04Z

David Kergyl: /* Adobe Flash Player (AFP) */

.

== great job ==

I noticed you're doing an enormous amount of work on the wiki. Thanks! [[User:Bernie|bernie]] 12:09, 17 March 2009 (UTC)

== table of contents ==

I wonder if we could configure mediawiki to always display the content table on the right instead of littering all the pages with the same directive? [[User:Bernie|bernie]]
:I haven't found anything like that yet. It's better as the template call than the full instruction:
<code><nowiki>{| cellspacing="0" cellpadding="0" style="clear:right; margin-bottom: .5em; float: right; padding: .5em 0 .8em 1.4em; background: none; width: {{{1|auto}}};"
| __TOC__
|}<noinclude>
[[Category:TOC templates|{{PAGENAME}}]]
</noinclude></nowiki></code> --[[User:FGrose|FGrose]] 23:52, 17 March 2009 (UTC)

== Adobe Flash Player (AFP) ==

Many thanks for your help. I think this information about AFP should be available through a link somewhere on this wiki. If you let me know where it should go, I'll take a stab at putting it in. [[User:David Kergyl|David Kergyl]] 19:55, 11 March 2010 (UTC)
*:Done! At least it's a start. [[User:David Kergyl|David Kergyl]] 19:28, 13 March 2010 (UTC)

Windows

2010-03-13T19:11:36Z

David Kergyl: /* A Sugar installer for Windows */ Clarify that the simple Sugar installer doesn't install any Activities.

{{Stub}}

==Sugar on Windows==

No one has ported Sugar to Windows (that we know of) but you can run Sugar on GNU/Linux in an emulator on top of a Windows System.

'''Note:''' Alternatively, you can boot your Windows machine with a Sugar LiveCD or LiveUSB—this will enable you to run Sugar without making any modifications to your Windows machine. See [[Supported_systems#Starch]].)

'''Note:''' The Wine Activity lets you run many Windows applications from within Sugar.

=== A Sugar installer for Windows ===

Wade Brainerd wrote a simple Sugar installer for Windows:

* [http://dev.laptop.org/~wadeb/OLPC-XO-Software-8.2.0-Setup.exe OLPC-XO-Software-8.2.0-Setup.exe] 07-Nov-2008

It installs/uninstalls a working Sugar environment (based on Ton van Overbeek's QEMU—See below) with just a few clicks. (Unfortunately, it does not install any Activities to use in that environment.)

The installer was built using the open source installer creator NSIS (nsis.sourceforge.net). The installer script can be found here:
[http://dev.laptop.org/git/users/wadeb/wininstall/.git wininstall/.git]

'''Note to build administrators:''' NSIS exists for GNU/Linux, so this process of creating Windows installers for Sugar could be automated.

=== Running Sugar in an emulator ===
* [[VirtualBox]], [[VMware]], [[QEMU]]
* [[Emulator image files]]
* [http://lists.laptop.org/pipermail/devel/2008-September/019643.html Tom van Overbeek describes how to run Sugar using QEMU]
* [http://www.nongnu.org/qemu/user-doc.html General information on using QEMU]

=== See also ===
* [http://wiki.laptop.org/go/Sugar_on_Windows OLPC Sugar on Windows]

[[Category:Supported systems]]

Adobe Flash

2010-03-13T18:47:07Z

David Kergyl: Adobe Flash - Add links to discussion threads.

This page is about '''Adobe Flash''', a proprietary player for Flash media. For the free software player that comes with Sugar, see Gnash (need sugarlabs link).

==Overview==

'' [http://www.adobe.com/products/flashplayer/ Adobe Flash] '' 10 can be installed for both the Browse Activity and the Opera activity. This installation must be repeated after any update.

Instructions for installing Adobe Flash can be found on the OLPC wiki at [http://wiki.laptop.org/go/Adobe_Flash Adobe Flash].

==Related Links==

[http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg12539.html Running SWF files standalone in Sugar]

http://blog.tomeuvizoso.net/2009/05/progress-on-sugar-activities-with-swf.html

http://blog.tomeuvizoso.net/2009/04/embed-flash-movies-with-gnash-in-your.html

Adobe Flash

2010-03-13T18:36:14Z

David Kergyl: Adobe Flash - Create page; add link to OLPC site.

Windows

2010-03-13T18:13:56Z

David Kergyl: /* See also */ Add OLPC.

{{Stub}}

==Sugar on Windows==

No one has ported Sugar to Windows (that we know of) but you can run Sugar on GNU/Linux in an emulator on top of a Windows System.

'''Note:''' Alternatively, you can boot your Windows machine with a Sugar LiveCD or LiveUSB—this will enable you to run Sugar without making any modifications to your Windows machine. See [[Supported_systems#Starch]].)

'''Note:''' The Wine Activity lets you run many Windows applications from within Sugar.

=== A Sugar installer for Windows ===
Wade Brainerd wrote a simple Sugar installer for Windows:

* [http://dev.laptop.org/~wadeb/OLPC-XO-Software-8.2.0-Setup.exe OLPC-XO-Software-8.2.0-Setup.exe] 07-Nov-2008

It installs/uninstalls a working Sugar environment (based on Ton van Overbeek's QEMU—See below) with just a few clicks.

The installer was built using the open source installer creator NSIS (nsis.sourceforge.net). The installer script can be found here:
[http://dev.laptop.org/git/users/wadeb/wininstall/.git wininstall/.git]

'''Note to build administrators:''' NSIS exists for GNU/Linux, so this process of creating Windows installers for Sugar could be automated.

=== Running Sugar in an emulator ===
* [[VirtualBox]], [[VMware]], [[QEMU]]
* [[Emulator image files]]
* [http://lists.laptop.org/pipermail/devel/2008-September/019643.html Tom van Overbeek describes how to run Sugar using QEMU]
* [http://www.nongnu.org/qemu/user-doc.html General information on using QEMU]

=== See also ===
* [http://wiki.laptop.org/go/Sugar_on_Windows OLPC Sugar on Windows]

[[Category:Supported systems]]

What could I do in an hour?

2010-03-13T18:02:08Z

David Kergyl: /* Edit the wiki */ And Live CD is very outdated.

<noinclude>{{TOCright}}
[[Category:Participate]]
</noinclude>
<div style="font-size: 1.7em; background: #ffffff; padding: 10px;" align=left>Contribute an hour of your time</div>
==Contribute to the wiki—It's your wiki!==
====Review the wiki====
:Please take a hour to explore the wiki, learn what's there, and then consider what's missing.
:At your next opportunity, enter that missing piece!

:It's your collective intelligence and contributions that make wikis work well.

::''Thank you for your contributions!''

====Update/remove old content on wiki.laptop.org====

[http://wiki.laptop.org/ wiki.laptop.org] contains a lot of information about Sugar that is outdated, while more up-to-date and more complete pages on the same topic can often be found on this wiki (the Sugar Labs one). Please consider reviewing those old pages and either replacing them by links to the appropriate Sugar Labs wiki pages (preferred) or updating them (with the risk of them getting out of sync again).

*A good starting point are the [http://wiki.laptop.org/go/Category:Installing_Sugar "Installing Sugar" pages]. Those often recommend using an "emulated XO" or running sugar-jhbuild. But as [[Downloads]] shows, the recommended ways to get Sugar (for non-developers) is to either burn [[Sugar on a Stick]] or install distribution packages.

====Edit the wiki====
* Please find a wiki page that interests you—and could be improved with something you know or could explain more clearly.

* It's simple to click the edit tab/button, and enter some new text or links, or whatever you want. Don't worry about making a mistake with the formating, others will come along to fix things up.

* If you don't want to edit the page directly, each page has a matching 'discussion' page, which you can reach by clicking the 'discussion' tab/button at the top. These pages are meant to collect reader comments and questions relevant to the parent page. See for example, [[Talk:Welcome to the Sugar Labs wiki]].
*: Remember to click the 'Watch' tab button so you will be notified of changes to the page. When you register your email with you account name, you can also click the [[Special:Preferences|'prefs']] (preferences) link at the top right of any page, and then, on the [[Special:Preferences#prefsection-7|'Watchlist']] tab page, you can set a preference to add any page you edit to your personal watchlist.

* If you want to enter whole new content pages, there are some guidelines at [[Wiki Team/Guide/Page Creation]]. There are instructions there for experimenting with new pages in you personal 'User_talk:' section of the wiki.
*: By this means, you can share and collaborate on whole projects in the Sugar Labs fields of interest, like Ed Cherlin's [[Education Team/Creating textbooks|Creating textbooks]].

* Some wiki pages can be improved by eliminating redundancies and adding cross-references.
*:For example, currently redundant and/or contradictory help information is present at both [[Sugar help]] and [[Sugar on a Stick/Blueberry|Get help!]].
*:And [[Live CD]] is very outdated.

====Edit the Sugar Learners' manual====
The [http://en.flossmanuals.net/Sugar Sugar Learners' manual] needs to be updated to include information regarding Sugar-on-a-Stick.

====New ideas, questions, or problems====
Some of our wiki pages are meant to collect new ideas, questions, or problems:

| [[Request New Features]] | [[Sugar help#Help Requests:]] | [[Submit Bugs/Problems]] |

== Visit our [[Vacancies]] page ==
* Consider whether you might be able to fill a [[Vacancies|vacancy]].
==Prepare a demo==
* Create a short "How To" video of a Sugar or Sugar Activity feature. See [[Video Using Sugar]] and our [http://www.dailymotion.com/sugarlabs channel on dailymotion.com].
* Create a short guide to using a Sugar activity to enhance a learning goal.

== Review Activities in the [http://activities.sugarlabs.org Sugar Activity Library] ==

* Download and try out the Activities on http://activities.sugarlabs.org, especially those that are new or recently updated.
* If you find bugs, report them at http://bugs.sugarlabs.org/.
* If you have ideas for improvements file them as enhancements at the same site.
* If you find the Activity useful, why not rate it and review it at http://activities.sugarlabs.org? This will encourage the author and make the Activity more visible to others who visit the Activity Library.
* Help keep the wiki page for the Activity you like up-to-date, interesting, & useful. The Activity wiki pages are listed at [[Activities]].

==Offer community help on [[IRC]]==
:<wim-9397> hi i am on sugar on a stick
:<wim-9397> in vmware, where do i set my keyboard ... it is azerty
:<wim-9397> an "i dont know" would also be helpfull
:<wim-9397> then at least in know there is someone to react
:<wim-9397> no community help?

We could use more people hanging out to answer questions...even if just for an hour here and there.

==[Your suggested activity]==

Talk:Live CD

2010-03-13T18:00:41Z

David Kergyl: Outdated page?

== Outdated page? ==

This page is outdated.

Live CD

2010-03-13T17:58:51Z

David Kergyl: /* Where to get */ Add broken link note.

== What is on the cd? ==
The sugar-jhbuild live CD has a the most recent and complete working sugar system out of the box. Just download, burn and boot from the CD.
The cd also has:

* An out-of-the-box running sugar system.
* Gnome.
* Stable Debian package of sugar.
* Extra debugging tools
* Wireless drivers

You can access the extra window managers by pressing ctrl+alt+del and choosing them at Login Manager.

=== login information ===
Username : user 
Password : live

== Where to get ==
You can try the latest Sugar build with a sugar-jhbuild live CD available at
http://download.sugarlabs.org/sugar/liveimages/debian-jhbuild. (Broken link as of 12 Mar 2010.)

== How to build ==

The construction of the CD is pretty easy. Configuration is all done in the <tt>/livecd/conf</tt> directory, you can read how to do it [http://wiki.debian.org/DebianLive debian-live site], or go in [irc://irc.oftc.net/#debian-live IRC debian-live channel]

=== In non-Debian systems (Fedora, etc) ===
1. Get the live-helper source code
git clone git://git.debian.net/git/debian-live/live-helper.git live-helper

=== In Debian systems ===

1.
apt-get install live-helper
2.
svn co https://sugarlivecd.svn.sourceforge.net/svnroot/sugarlivecd
cd ./sugarlivecd/livecd
lh_clean ; lh_build

The creation takes time, and you will need to be connected to the internet.

What could I do in an hour?

2010-03-13T17:23:27Z

David Kergyl: /* Update/remove old content on wiki.laptop.org */ Formatting.

<noinclude>{{TOCright}}
[[Category:Participate]]
</noinclude>
<div style="font-size: 1.7em; background: #ffffff; padding: 10px;" align=left>Contribute an hour of your time</div>
==Contribute to the wiki—It's your wiki!==
====Review the wiki====
:Please take a hour to explore the wiki, learn what's there, and then consider what's missing.
:At your next opportunity, enter that missing piece!

:It's your collective intelligence and contributions that make wikis work well.

::''Thank you for your contributions!''

====Update/remove old content on wiki.laptop.org====

[http://wiki.laptop.org/ wiki.laptop.org] contains a lot of information about Sugar that is outdated, while more up-to-date and more complete pages on the same topic can often be found on this wiki (the Sugar Labs one). Please consider reviewing those old pages and either replacing them by links to the appropriate Sugar Labs wiki pages (preferred) or updating them (with the risk of them getting out of sync again).

*A good starting point are the [http://wiki.laptop.org/go/Category:Installing_Sugar "Installing Sugar" pages]. Those often recommend using an "emulated XO" or running sugar-jhbuild. But as [[Downloads]] shows, the recommended ways to get Sugar (for non-developers) is to either burn [[Sugar on a Stick]] or install distribution packages.

====Edit the wiki====
* Please find a wiki page that interests you—and could be improved with something you know or could explain more clearly.

* It's simple to click the edit tab/button, and enter some new text or links, or whatever you want. Don't worry about making a mistake with the formating, others will come along to fix things up.

* If you don't want to edit the page directly, each page has a matching 'discussion' page, which you can reach by clicking the 'discussion' tab/button at the top. These pages are meant to collect reader comments and questions relevant to the parent page. See for example, [[Talk:Welcome to the Sugar Labs wiki]].
*: Remember to click the 'Watch' tab button so you will be notified of changes to the page. When you register your email with you account name, you can also click the [[Special:Preferences|'prefs']] (preferences) link at the top right of any page, and then, on the [[Special:Preferences#prefsection-7|'Watchlist']] tab page, you can set a preference to add any page you edit to your personal watchlist.

* If you want to enter whole new content pages, there are some guidelines at [[Wiki Team/Guide/Page Creation]]. There are instructions there for experimenting with new pages in you personal 'User_talk:' section of the wiki.
*: By this means, you can share and collaborate on whole projects in the Sugar Labs fields of interest, like Ed Cherlin's [[Education Team/Creating textbooks|Creating textbooks]].

* Some wiki pages can be improved by eliminating redundancies and adding cross-references.
*:For example, currently redundant and/or contradictory help information is present at both [[Sugar help]] and [[Sugar on a Stick/Blueberry|Get help!]].

====Edit the Sugar Learners' manual====
The [http://en.flossmanuals.net/Sugar Sugar Learners' manual] needs to be updated to include information regarding Sugar-on-a-Stick.

====New ideas, questions, or problems====
Some of our wiki pages are meant to collect new ideas, questions, or problems:

| [[Request New Features]] | [[Sugar help#Help Requests:]] | [[Submit Bugs/Problems]] |

== Visit our [[Vacancies]] page ==
* Consider whether you might be able to fill a [[Vacancies|vacancy]].
==Prepare a demo==
* Create a short "How To" video of a Sugar or Sugar Activity feature. See [[Video Using Sugar]] and our [http://www.dailymotion.com/sugarlabs channel on dailymotion.com].
* Create a short guide to using a Sugar activity to enhance a learning goal.

== Review Activities in the [http://activities.sugarlabs.org Sugar Activity Library] ==

* Download and try out the Activities on http://activities.sugarlabs.org, especially those that are new or recently updated.
* If you find bugs, report them at http://bugs.sugarlabs.org/.
* If you have ideas for improvements file them as enhancements at the same site.
* If you find the Activity useful, why not rate it and review it at http://activities.sugarlabs.org? This will encourage the author and make the Activity more visible to others who visit the Activity Library.
* Help keep the wiki page for the Activity you like up-to-date, interesting, & useful. The Activity wiki pages are listed at [[Activities]].

==Offer community help on [[IRC]]==
:<wim-9397> hi i am on sugar on a stick
:<wim-9397> in vmware, where do i set my keyboard ... it is azerty
:<wim-9397> an "i dont know" would also be helpfull
:<wim-9397> then at least in know there is someone to react
:<wim-9397> no community help?

We could use more people hanging out to answer questions...even if just for an hour here and there.

==[Your suggested activity]==

What could I do in an hour?

2010-03-13T16:06:16Z

David Kergyl: /* Review Activities in the Sugar Activity Library */ Correct link to Activities page.

<noinclude>{{TOCright}}
[[Category:Participate]]
</noinclude>
<div style="font-size: 1.7em; background: #ffffff; padding: 10px;" align=left>Contribute an hour of your time</div>
==Contribute to the wiki—It's your wiki!==
====Review the wiki====
:Please take a hour to explore the wiki, learn what's there, and then consider what's missing.
:At your next opportunity, enter that missing piece!

:It's your collective intelligence and contributions that make wikis work well.

::''Thank you for your contributions!''

====Update/remove old content on wiki.laptop.org====

[http://wiki.laptop.org/ wiki.laptop.org] contains a lot of information about Sugar that is outdated, while more up-to-date and more complete pages on the same topic can often be found on this wiki (the Sugar Labs one). Please consider reviewing those old pages and either replacing them by links to the appropriate Sugar Labs wiki pages (preferred) or updating them (with the risk of them getting out of sync again). A good starting point are the [http://wiki.laptop.org/go/Category:Installing_Sugar "Installing Sugar" pages]. Those often recommend using an "emulated XO" or running sugar-jhbuild. But as [[Downloads]] shows, the recommended ways to get Sugar (for non-developers) is to either burn [[Sugar on a Stick]] or install distribution packages.

====Edit the wiki====
* Please find a wiki page that interests you—and could be improved with something you know or could explain more clearly.

* It's simple to click the edit tab/button, and enter some new text or links, or whatever you want. Don't worry about making a mistake with the formating, others will come along to fix things up.

* If you don't want to edit the page directly, each page has a matching 'discussion' page, which you can reach by clicking the 'discussion' tab/button at the top. These pages are meant to collect reader comments and questions relevant to the parent page. See for example, [[Talk:Welcome to the Sugar Labs wiki]].
*: Remember to click the 'Watch' tab button so you will be notified of changes to the page. When you register your email with you account name, you can also click the [[Special:Preferences|'prefs']] (preferences) link at the top right of any page, and then, on the [[Special:Preferences#prefsection-7|'Watchlist']] tab page, you can set a preference to add any page you edit to your personal watchlist.

* If you want to enter whole new content pages, there are some guidelines at [[Wiki Team/Guide/Page Creation]]. There are instructions there for experimenting with new pages in you personal 'User_talk:' section of the wiki.
*: By this means, you can share and collaborate on whole projects in the Sugar Labs fields of interest, like Ed Cherlin's [[Education Team/Creating textbooks|Creating textbooks]].

* Some wiki pages can be improved by eliminating redundancies and adding cross-references.
*:For example, currently redundant and/or contradictory help information is present at both [[Sugar help]] and [[Sugar on a Stick/Blueberry|Get help!]].

====Edit the Sugar Learners' manual====
The [http://en.flossmanuals.net/Sugar Sugar Learners' manual] needs to be updated to include information regarding Sugar-on-a-Stick.

====New ideas, questions, or problems====
Some of our wiki pages are meant to collect new ideas, questions, or problems:

| [[Request New Features]] | [[Sugar help#Help Requests:]] | [[Submit Bugs/Problems]] |

== Visit our [[Vacancies]] page ==
* Consider whether you might be able to fill a [[Vacancies|vacancy]].
==Prepare a demo==
* Create a short "How To" video of a Sugar or Sugar Activity feature. See [[Video Using Sugar]] and our [http://www.dailymotion.com/sugarlabs channel on dailymotion.com].
* Create a short guide to using a Sugar activity to enhance a learning goal.

== Review Activities in the [http://activities.sugarlabs.org Sugar Activity Library] ==

* Download and try out the Activities on http://activities.sugarlabs.org, especially those that are new or recently updated.
* If you find bugs, report them at http://bugs.sugarlabs.org/.
* If you have ideas for improvements file them as enhancements at the same site.
* If you find the Activity useful, why not rate it and review it at http://activities.sugarlabs.org? This will encourage the author and make the Activity more visible to others who visit the Activity Library.
* Help keep the wiki page for the Activity you like up-to-date, interesting, & useful. The Activity wiki pages are listed at [[Activities]].

==Offer community help on [[IRC]]==
:<wim-9397> hi i am on sugar on a stick
:<wim-9397> in vmware, where do i set my keyboard ... it is azerty
:<wim-9397> an "i dont know" would also be helpfull
:<wim-9397> then at least in know there is someone to react
:<wim-9397> no community help?

We could use more people hanging out to answer questions...even if just for an hour here and there.

==[Your suggested activity]==

What could I do in an hour?

2010-03-13T16:02:12Z

David Kergyl: /* Review Activities in the Sugar Activity Library */ Correct link to Activities.

<noinclude>{{TOCright}}
[[Category:Participate]]
</noinclude>
<div style="font-size: 1.7em; background: #ffffff; padding: 10px;" align=left>Contribute an hour of your time</div>
==Contribute to the wiki—It's your wiki!==
====Review the wiki====
:Please take a hour to explore the wiki, learn what's there, and then consider what's missing.
:At your next opportunity, enter that missing piece!

:It's your collective intelligence and contributions that make wikis work well.

::''Thank you for your contributions!''

====Update/remove old content on wiki.laptop.org====

[http://wiki.laptop.org/ wiki.laptop.org] contains a lot of information about Sugar that is outdated, while more up-to-date and more complete pages on the same topic can often be found on this wiki (the Sugar Labs one). Please consider reviewing those old pages and either replacing them by links to the appropriate Sugar Labs wiki pages (preferred) or updating them (with the risk of them getting out of sync again). A good starting point are the [http://wiki.laptop.org/go/Category:Installing_Sugar "Installing Sugar" pages]. Those often recommend using an "emulated XO" or running sugar-jhbuild. But as [[Downloads]] shows, the recommended ways to get Sugar (for non-developers) is to either burn [[Sugar on a Stick]] or install distribution packages.

====Edit the wiki====
* Please find a wiki page that interests you—and could be improved with something you know or could explain more clearly.

* It's simple to click the edit tab/button, and enter some new text or links, or whatever you want. Don't worry about making a mistake with the formating, others will come along to fix things up.

* If you don't want to edit the page directly, each page has a matching 'discussion' page, which you can reach by clicking the 'discussion' tab/button at the top. These pages are meant to collect reader comments and questions relevant to the parent page. See for example, [[Talk:Welcome to the Sugar Labs wiki]].
*: Remember to click the 'Watch' tab button so you will be notified of changes to the page. When you register your email with you account name, you can also click the [[Special:Preferences|'prefs']] (preferences) link at the top right of any page, and then, on the [[Special:Preferences#prefsection-7|'Watchlist']] tab page, you can set a preference to add any page you edit to your personal watchlist.

* If you want to enter whole new content pages, there are some guidelines at [[Wiki Team/Guide/Page Creation]]. There are instructions there for experimenting with new pages in you personal 'User_talk:' section of the wiki.
*: By this means, you can share and collaborate on whole projects in the Sugar Labs fields of interest, like Ed Cherlin's [[Education Team/Creating textbooks|Creating textbooks]].

* Some wiki pages can be improved by eliminating redundancies and adding cross-references.
*:For example, currently redundant and/or contradictory help information is present at both [[Sugar help]] and [[Sugar on a Stick/Blueberry|Get help!]].

====Edit the Sugar Learners' manual====
The [http://en.flossmanuals.net/Sugar Sugar Learners' manual] needs to be updated to include information regarding Sugar-on-a-Stick.

====New ideas, questions, or problems====
Some of our wiki pages are meant to collect new ideas, questions, or problems:

| [[Request New Features]] | [[Sugar help#Help Requests:]] | [[Submit Bugs/Problems]] |

== Visit our [[Vacancies]] page ==
* Consider whether you might be able to fill a [[Vacancies|vacancy]].
==Prepare a demo==
* Create a short "How To" video of a Sugar or Sugar Activity feature. See [[Video Using Sugar]] and our [http://www.dailymotion.com/sugarlabs channel on dailymotion.com].
* Create a short guide to using a Sugar activity to enhance a learning goal.

== Review Activities in the [http://activities.sugarlabs.org Sugar Activity Library] ==

* Download and try out the Activities on http://activities.sugarlabs.org, especially those that are new or recently updated.
* If you find bugs, report them at http://bugs.sugarlabs.org/.
* If you have ideas for improvements file them as enhancements at the same site.
* If you find the Activity useful, why not rate it and review it at http://activities.sugarlabs.org? This will encourage the author and make the Activity more visible to others who visit the Activity Library.
* Help keep the wiki page for the Activity you like up-to-date, interesting, & useful. The Activity wiki pages are at [[:Category:Activities]].

==Offer community help on [[IRC]]==
:<wim-9397> hi i am on sugar on a stick
:<wim-9397> in vmware, where do i set my keyboard ... it is azerty
:<wim-9397> an "i dont know" would also be helpfull
:<wim-9397> then at least in know there is someone to react
:<wim-9397> no community help?

We could use more people hanging out to answer questions...even if just for an hour here and there.

==[Your suggested activity]==

What could I do in an hour?

2010-03-13T15:58:50Z

David Kergyl: /* Review Activities in the Sugar Activity Library */ Add link to the Activities pages.

<noinclude>{{TOCright}}
[[Category:Participate]]
</noinclude>
<div style="font-size: 1.7em; background: #ffffff; padding: 10px;" align=left>Contribute an hour of your time</div>
==Contribute to the wiki—It's your wiki!==
====Review the wiki====
:Please take a hour to explore the wiki, learn what's there, and then consider what's missing.
:At your next opportunity, enter that missing piece!

:It's your collective intelligence and contributions that make wikis work well.

::''Thank you for your contributions!''

====Update/remove old content on wiki.laptop.org====

[http://wiki.laptop.org/ wiki.laptop.org] contains a lot of information about Sugar that is outdated, while more up-to-date and more complete pages on the same topic can often be found on this wiki (the Sugar Labs one). Please consider reviewing those old pages and either replacing them by links to the appropriate Sugar Labs wiki pages (preferred) or updating them (with the risk of them getting out of sync again). A good starting point are the [http://wiki.laptop.org/go/Category:Installing_Sugar "Installing Sugar" pages]. Those often recommend using an "emulated XO" or running sugar-jhbuild. But as [[Downloads]] shows, the recommended ways to get Sugar (for non-developers) is to either burn [[Sugar on a Stick]] or install distribution packages.

====Edit the wiki====
* Please find a wiki page that interests you—and could be improved with something you know or could explain more clearly.

* It's simple to click the edit tab/button, and enter some new text or links, or whatever you want. Don't worry about making a mistake with the formating, others will come along to fix things up.

* If you don't want to edit the page directly, each page has a matching 'discussion' page, which you can reach by clicking the 'discussion' tab/button at the top. These pages are meant to collect reader comments and questions relevant to the parent page. See for example, [[Talk:Welcome to the Sugar Labs wiki]].
*: Remember to click the 'Watch' tab button so you will be notified of changes to the page. When you register your email with you account name, you can also click the [[Special:Preferences|'prefs']] (preferences) link at the top right of any page, and then, on the [[Special:Preferences#prefsection-7|'Watchlist']] tab page, you can set a preference to add any page you edit to your personal watchlist.

* If you want to enter whole new content pages, there are some guidelines at [[Wiki Team/Guide/Page Creation]]. There are instructions there for experimenting with new pages in you personal 'User_talk:' section of the wiki.
*: By this means, you can share and collaborate on whole projects in the Sugar Labs fields of interest, like Ed Cherlin's [[Education Team/Creating textbooks|Creating textbooks]].

* Some wiki pages can be improved by eliminating redundancies and adding cross-references.
*:For example, currently redundant and/or contradictory help information is present at both [[Sugar help]] and [[Sugar on a Stick/Blueberry|Get help!]].

====Edit the Sugar Learners' manual====
The [http://en.flossmanuals.net/Sugar Sugar Learners' manual] needs to be updated to include information regarding Sugar-on-a-Stick.

====New ideas, questions, or problems====
Some of our wiki pages are meant to collect new ideas, questions, or problems:

| [[Request New Features]] | [[Sugar help#Help Requests:]] | [[Submit Bugs/Problems]] |

== Visit our [[Vacancies]] page ==
* Consider whether you might be able to fill a [[Vacancies|vacancy]].
==Prepare a demo==
* Create a short "How To" video of a Sugar or Sugar Activity feature. See [[Video Using Sugar]] and our [http://www.dailymotion.com/sugarlabs channel on dailymotion.com].
* Create a short guide to using a Sugar activity to enhance a learning goal.

== Review Activities in the [http://activities.sugarlabs.org Sugar Activity Library] ==

* Download and try out the Activities on http://activities.sugarlabs.org, especially those that are new or recently updated.
* If you find bugs, report them at http://bugs.sugarlabs.org/.
* If you have ideas for improvements file them as enhancements at the same site.
* If you find the Activity useful, why not rate it and review it at http://activities.sugarlabs.org? This will encourage the author and make the Activity more visible to others who visit the Activity Library.
* Help keep the [[Category:Activities]] wiki page for the Activity you like up-to-date, interesting, & useful.

==Offer community help on [[IRC]]==
:<wim-9397> hi i am on sugar on a stick
:<wim-9397> in vmware, where do i set my keyboard ... it is azerty
:<wim-9397> an "i dont know" would also be helpfull
:<wim-9397> then at least in know there is someone to react
:<wim-9397> no community help?

We could use more people hanging out to answer questions...even if just for an hour here and there.

==[Your suggested activity]==

What could I do in an hour?

2010-03-13T15:53:31Z

David Kergyl: /* Edit the wiki */ Add comment regarding help redundancy.

<noinclude>{{TOCright}}
[[Category:Participate]]
</noinclude>
<div style="font-size: 1.7em; background: #ffffff; padding: 10px;" align=left>Contribute an hour of your time</div>
==Contribute to the wiki—It's your wiki!==
====Review the wiki====
:Please take a hour to explore the wiki, learn what's there, and then consider what's missing.
:At your next opportunity, enter that missing piece!

:It's your collective intelligence and contributions that make wikis work well.

::''Thank you for your contributions!''

====Update/remove old content on wiki.laptop.org====

[http://wiki.laptop.org/ wiki.laptop.org] contains a lot of information about Sugar that is outdated, while more up-to-date and more complete pages on the same topic can often be found on this wiki (the Sugar Labs one). Please consider reviewing those old pages and either replacing them by links to the appropriate Sugar Labs wiki pages (preferred) or updating them (with the risk of them getting out of sync again). A good starting point are the [http://wiki.laptop.org/go/Category:Installing_Sugar "Installing Sugar" pages]. Those often recommend using an "emulated XO" or running sugar-jhbuild. But as [[Downloads]] shows, the recommended ways to get Sugar (for non-developers) is to either burn [[Sugar on a Stick]] or install distribution packages.

====Edit the wiki====
* Please find a wiki page that interests you—and could be improved with something you know or could explain more clearly.

* It's simple to click the edit tab/button, and enter some new text or links, or whatever you want. Don't worry about making a mistake with the formating, others will come along to fix things up.

* If you don't want to edit the page directly, each page has a matching 'discussion' page, which you can reach by clicking the 'discussion' tab/button at the top. These pages are meant to collect reader comments and questions relevant to the parent page. See for example, [[Talk:Welcome to the Sugar Labs wiki]].
*: Remember to click the 'Watch' tab button so you will be notified of changes to the page. When you register your email with you account name, you can also click the [[Special:Preferences|'prefs']] (preferences) link at the top right of any page, and then, on the [[Special:Preferences#prefsection-7|'Watchlist']] tab page, you can set a preference to add any page you edit to your personal watchlist.

* If you want to enter whole new content pages, there are some guidelines at [[Wiki Team/Guide/Page Creation]]. There are instructions there for experimenting with new pages in you personal 'User_talk:' section of the wiki.
*: By this means, you can share and collaborate on whole projects in the Sugar Labs fields of interest, like Ed Cherlin's [[Education Team/Creating textbooks|Creating textbooks]].

* Some wiki pages can be improved by eliminating redundancies and adding cross-references.
*:For example, currently redundant and/or contradictory help information is present at both [[Sugar help]] and [[Sugar on a Stick/Blueberry|Get help!]].

====Edit the Sugar Learners' manual====
The [http://en.flossmanuals.net/Sugar Sugar Learners' manual] needs to be updated to include information regarding Sugar-on-a-Stick.

====New ideas, questions, or problems====
Some of our wiki pages are meant to collect new ideas, questions, or problems:

| [[Request New Features]] | [[Sugar help#Help Requests:]] | [[Submit Bugs/Problems]] |

== Visit our [[Vacancies]] page ==
* Consider whether you might be able to fill a [[Vacancies|vacancy]].
==Prepare a demo==
* Create a short "How To" video of a Sugar or Sugar Activity feature. See [[Video Using Sugar]] and our [http://www.dailymotion.com/sugarlabs channel on dailymotion.com].
* Create a short guide to using a Sugar activity to enhance a learning goal.

== Review Activities in the [http://activities.sugarlabs.org Sugar Activity Library] ==

* Download and try out the Activities on http://activities.sugarlabs.org, especially those that are new or recently updated.
* If you find bugs, report them at http://bugs.sugarlabs.org/.
* If you have ideas for improvements file them as enhancements at the same site.
* If you find the Activity useful, why not rate it and review it at http://activities.sugarlabs.org? This will encourage the author and make the Activity more visible to others who visit the Activity Library.
* Help keep the wiki page for the Activity you like up-to-date, interesting, & useful.

==Offer community help on [[IRC]]==
:<wim-9397> hi i am on sugar on a stick
:<wim-9397> in vmware, where do i set my keyboard ... it is azerty
:<wim-9397> an "i dont know" would also be helpfull
:<wim-9397> then at least in know there is someone to react
:<wim-9397> no community help?

We could use more people hanging out to answer questions...even if just for an hour here and there.

==[Your suggested activity]==

Talk:Sugar on a Stick/Blueberry

2010-03-13T15:43:15Z

David Kergyl: /* Get help section is redundant to Sugar_help page */ new section

== md5sum doesn't match ==

SHA1SUM file from download directory does...

[[User:Danceswithcars|Danceswithcars]] 15:31, 12 December 2009 (UTC)

== Loading WiFi driver for Classmate 3 ==
1. Download rt2870.bin from ralinktech.com (Be sure to download the Linux version).

2. Copy the .bin file into /lib/firmware
cp rt2870.bin /lib/firmware

3. You need to load the RPM Fusion repository for Fedora
sudo rpm -i http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
or
sudo rpm -i http://bit.ly/Fs7c7

4. yum install the driver
sudo yum install akmod-rt2870

'''Note:''' Step 4 is going to eat up lots of disk space.

== Get help section is redundant to Sugar_help page ==

This help section should perhaps be moved to the general Sugar_help page, or be limited specifically to help with Sugar-on-a-Stick, and be cross-referenced to that page. There's a lot of redundant information here.

Also, Is the answers portal still recommended for use? The Sugar_help page doesn't link there or suggest its use.

What could I do in an hour?

2010-03-12T18:27:39Z

David Kergyl: /* Edit the user manual */

<noinclude>{{TOCright}}
[[Category:Participate]]
</noinclude>
<div style="font-size: 1.7em; background: #ffffff; padding: 10px;" align=left>Contribute an hour of your time</div>
==Contribute to the wiki—It's your wiki!==
====Review the wiki====
:Please take a hour to explore the wiki, learn what's there, and then consider what's missing.
:At your next opportunity, enter that missing piece!

:It's your collective intelligence and contributions that make wikis work well.

::''Thank you for your contributions!''

====Update/remove old content on wiki.laptop.org====

[http://wiki.laptop.org/ wiki.laptop.org] contains a lot of information about Sugar that is outdated, while more up-to-date and more complete pages on the same topic can often be found on this wiki (the Sugar Labs one). Please consider reviewing those old pages and either replacing them by links to the appropriate Sugar Labs wiki pages (preferred) or updating them (with the risk of them getting out of sync again). A good starting point are the [http://wiki.laptop.org/go/Category:Installing_Sugar "Installing Sugar" pages]. Those often recommend using an "emulated XO" or running sugar-jhbuild. But as [[Downloads]] shows, the recommended ways to get Sugar (for non-developers) is to either burn [[Sugar on a Stick]] or install distribution packages.

====Edit the wiki====
* Please find a wiki page that interests you—and could be improved with something you know or could explain more clearly.

* It's simple to click the edit tab/button, and enter some new text or links, or whatever you want. Don't worry about making a mistake with the formating, others will come along to fix things up.

* If you don't want to edit the page directly, each page has a matching 'discussion' page, which you can reach by clicking the 'discussion' tab/button at the top. These pages are meant to collect reader comments and questions relevant to the parent page. See for example, [[Talk:Welcome to the Sugar Labs wiki]].
*: Remember to click the 'Watch' tab button so you will be notified of changes to the page. When you register your email with you account name, you can also click the [[Special:Preferences|'prefs']] (preferences) link at the top right of any page, and then, on the [[Special:Preferences#prefsection-7|'Watchlist']] tab page, you can set a preference to add any page you edit to your personal watchlist.

* If you want to enter whole new content pages, there are some guidelines at [[Wiki Team/Guide/Page Creation]]. There are instructions there for experimenting with new pages in you personal 'User_talk:' section of the wiki.
*: By this means, you can share and collaborate on whole projects in the Sugar Labs fields of interest, like Ed Cherlin's [[Education Team/Creating textbooks|Creating textbooks]].

====Edit the Sugar Learners' manual====
The [http://en.flossmanuals.net/Sugar Sugar Learners' manual] needs to be updated to include information regarding Sugar-on-a-Stick.

====New ideas, questions, or problems====
Some of our wiki pages are meant to collect new ideas, questions, or problems:

| [[Request New Features]] | [[Sugar help#Help Requests:]] | [[Submit Bugs/Problems]] |

== Visit our [[Vacancies]] page ==
* Consider whether you might be able to fill a [[Vacancies|vacancy]].
==Prepare a demo==
* Create a short "How To" video of a Sugar or Sugar Activity feature. See [[Video Using Sugar]] and our [http://www.dailymotion.com/sugarlabs channel on dailymotion.com].
* Create a short guide to using a Sugar activity to enhance a learning goal.

== Review Activities in the [http://activities.sugarlabs.org Sugar Activity Library] ==

* Download and try out the Activities on http://activities.sugarlabs.org, especially those that are new or recently updated.
* If you find bugs, report them at http://bugs.sugarlabs.org/.
* If you have ideas for improvements file them as enhancements at the same site.
* If you find the Activity useful, why not rate it and review it at http://activities.sugarlabs.org? This will encourage the author and make the Activity more visible to others who visit the Activity Library.
* Help keep the wiki page for the Activity you like up-to-date, interesting, & useful.

==Offer community help on [[IRC]]==
:<wim-9397> hi i am on sugar on a stick
:<wim-9397> in vmware, where do i set my keyboard ... it is azerty
:<wim-9397> an "i dont know" would also be helpfull
:<wim-9397> then at least in know there is someone to react
:<wim-9397> no community help?

We could use more people hanging out to answer questions...even if just for an hour here and there.

==[Your suggested activity]==

What could I do in an hour?

2010-03-12T18:26:02Z

David Kergyl: /* Contribute to the wiki—It's your wiki! */

<noinclude>{{TOCright}}
[[Category:Participate]]
</noinclude>
<div style="font-size: 1.7em; background: #ffffff; padding: 10px;" align=left>Contribute an hour of your time</div>
==Contribute to the wiki—It's your wiki!==
====Review the wiki====
:Please take a hour to explore the wiki, learn what's there, and then consider what's missing.
:At your next opportunity, enter that missing piece!

:It's your collective intelligence and contributions that make wikis work well.

::''Thank you for your contributions!''

====Update/remove old content on wiki.laptop.org====

[http://wiki.laptop.org/ wiki.laptop.org] contains a lot of information about Sugar that is outdated, while more up-to-date and more complete pages on the same topic can often be found on this wiki (the Sugar Labs one). Please consider reviewing those old pages and either replacing them by links to the appropriate Sugar Labs wiki pages (preferred) or updating them (with the risk of them getting out of sync again). A good starting point are the [http://wiki.laptop.org/go/Category:Installing_Sugar "Installing Sugar" pages]. Those often recommend using an "emulated XO" or running sugar-jhbuild. But as [[Downloads]] shows, the recommended ways to get Sugar (for non-developers) is to either burn [[Sugar on a Stick]] or install distribution packages.

====Edit the wiki====
* Please find a wiki page that interests you—and could be improved with something you know or could explain more clearly.

* It's simple to click the edit tab/button, and enter some new text or links, or whatever you want. Don't worry about making a mistake with the formating, others will come along to fix things up.

* If you don't want to edit the page directly, each page has a matching 'discussion' page, which you can reach by clicking the 'discussion' tab/button at the top. These pages are meant to collect reader comments and questions relevant to the parent page. See for example, [[Talk:Welcome to the Sugar Labs wiki]].
*: Remember to click the 'Watch' tab button so you will be notified of changes to the page. When you register your email with you account name, you can also click the [[Special:Preferences|'prefs']] (preferences) link at the top right of any page, and then, on the [[Special:Preferences#prefsection-7|'Watchlist']] tab page, you can set a preference to add any page you edit to your personal watchlist.

* If you want to enter whole new content pages, there are some guidelines at [[Wiki Team/Guide/Page Creation]]. There are instructions there for experimenting with new pages in you personal 'User_talk:' section of the wiki.
*: By this means, you can share and collaborate on whole projects in the Sugar Labs fields of interest, like Ed Cherlin's [[Education Team/Creating textbooks|Creating textbooks]].

====Edit the user manual====
The [http://en.flossmanuals.net/Sugar The Sugar Learners' manual] needs to be updated to include information regarding Sugar-on-a-Stick.

====New ideas, questions, or problems====
Some of our wiki pages are meant to collect new ideas, questions, or problems:

| [[Request New Features]] | [[Sugar help#Help Requests:]] | [[Submit Bugs/Problems]] |

== Visit our [[Vacancies]] page ==
* Consider whether you might be able to fill a [[Vacancies|vacancy]].
==Prepare a demo==
* Create a short "How To" video of a Sugar or Sugar Activity feature. See [[Video Using Sugar]] and our [http://www.dailymotion.com/sugarlabs channel on dailymotion.com].
* Create a short guide to using a Sugar activity to enhance a learning goal.

== Review Activities in the [http://activities.sugarlabs.org Sugar Activity Library] ==

* Download and try out the Activities on http://activities.sugarlabs.org, especially those that are new or recently updated.
* If you find bugs, report them at http://bugs.sugarlabs.org/.
* If you have ideas for improvements file them as enhancements at the same site.
* If you find the Activity useful, why not rate it and review it at http://activities.sugarlabs.org? This will encourage the author and make the Activity more visible to others who visit the Activity Library.
* Help keep the wiki page for the Activity you like up-to-date, interesting, & useful.

==Offer community help on [[IRC]]==
:<wim-9397> hi i am on sugar on a stick
:<wim-9397> in vmware, where do i set my keyboard ... it is azerty
:<wim-9397> an "i dont know" would also be helpfull
:<wim-9397> then at least in know there is someone to react
:<wim-9397> no community help?

We could use more people hanging out to answer questions...even if just for an hour here and there.

==[Your suggested activity]==

Talk:Sugar on a Stick/ZyX-LiveInstaller

2010-03-12T17:59:34Z

David Kergyl: /* Superuser needed? */

== Superuser needed? ==

Shouldn't "Type: <code>zyx-liveinstaller</code>" be "Type: <code>sudo zyx-liveinstaller</code>"? [[User:David Kergyl|David Kergyl]] 17:59, 12 March 2010 (UTC)

== alternative instructions ==
[[Image:Zyx-banner.png|300px]]

ZyX-LiveInstaller allows you to install Sugar from either a LiveUSB device or LiveCD media to a system or external disk, in order to create a traditional operating system installation on disk (or removable media such as SD or USB storage devices).

'''Note:''' This is ''not'' a method for creating a Sugar-on-a-Stick (LiveUSB) image. Although you can install to an external USB drive/stick, resulting in an installation that similarly boots your system to the Sugar UI. The difference is that the resulting system is not a 'Live' system; it uses a normal filesystem instead of a compressed read-only filesystem and a read-write overlay.

'''IMPORTANT WARNING:''' This software will ''overwrite entire partitions or disks''—as well as your bootloader—during installation. It is ''currently'' intended only for users that are familiar with the risks and possible complications of installing a GNU/Linux distribution to system disk. If you need a dual-boot configuration, you will need to configure <code>grub</code> yourself.

To use the ZyX-LiveInstaller:
# Boot your target computer with Sugar-on-a-Stick;
# Run ZyX-LiveInstaller:
:* Start the Terminal activity;
:* Type: <code>zyx-liveinstaller</code>
:* Check that you have room on the target drive:
::* Run <code>gparted</code> from within ZyX-LiveInstaller
::*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 separate partition for the /boot filesystem, at least 42MB in size
::* Optionally create a separate partition for swap space, typically 1–2 times the size of the 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 the partitioner is not required; (does not work for VirtualBox use: /boot 200 ext2; / 3000 ext4; balance: linux-swap)
::* Exit the partitioner by hitting the X in the top corner of window.
:* While still in Zyx-LiveInstaller:
::* Read and follow the simple wizard, choosing destination volumes/partitions for root, boot, and swap.

Notes:
* This is a ''destructive'' install: ''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 [http://filteredperception.org/smiley/projects/zyx-liveinstaller].

Talk:Sugar on a Stick/ZyX-LiveInstaller

2010-03-12T17:58:27Z

David Kergyl:

== Superuser needed? ==

Shouldn't "Type: <code>zyx-liveinstaller</code>" be "Type: <code>sudo zyx-liveinstaller</code>"?

== alternative instructions ==
[[Image:Zyx-banner.png|300px]]

ZyX-LiveInstaller allows you to install Sugar from either a LiveUSB device or LiveCD media to a system or external disk, in order to create a traditional operating system installation on disk (or removable media such as SD or USB storage devices).

'''Note:''' This is ''not'' a method for creating a Sugar-on-a-Stick (LiveUSB) image. Although you can install to an external USB drive/stick, resulting in an installation that similarly boots your system to the Sugar UI. The difference is that the resulting system is not a 'Live' system; it uses a normal filesystem instead of a compressed read-only filesystem and a read-write overlay.

'''IMPORTANT WARNING:''' This software will ''overwrite entire partitions or disks''—as well as your bootloader—during installation. It is ''currently'' intended only for users that are familiar with the risks and possible complications of installing a GNU/Linux distribution to system disk. If you need a dual-boot configuration, you will need to configure <code>grub</code> yourself.

To use the ZyX-LiveInstaller:
# Boot your target computer with Sugar-on-a-Stick;
# Run ZyX-LiveInstaller:
:* Start the Terminal activity;
:* Type: <code>zyx-liveinstaller</code>
:* Check that you have room on the target drive:
::* Run <code>gparted</code> from within ZyX-LiveInstaller
::*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 separate partition for the /boot filesystem, at least 42MB in size
::* Optionally create a separate partition for swap space, typically 1–2 times the size of the 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 the partitioner is not required; (does not work for VirtualBox use: /boot 200 ext2; / 3000 ext4; balance: linux-swap)
::* Exit the partitioner by hitting the X in the top corner of window.
:* While still in Zyx-LiveInstaller:
::* Read and follow the simple wizard, choosing destination volumes/partitions for root, boot, and swap.

Notes:
* This is a ''destructive'' install: ''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 [http://filteredperception.org/smiley/projects/zyx-liveinstaller].

SoaS Blueberry Instructions

2010-03-12T17:31:18Z

David Kergyl: /* For Windows Users */ Add instructions for using Live CD and zyx-liveinstaller.

__NOTOC__

=== For Windows Users ===

Persons using PCs running Windows have two options for creating a Sugar/Blueberry USB flash drive:

::'''Option #1: Use LiveUSB Creator from within Windows to create a Sugar-on-a-Stick Live USB with a compressed filesystem.'''

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: white;"
|-
|valign=top|[[Image:fedora-liveusb-creator.png|left|300px]]
|valign=top|
# Download the latest version of the '''Fedora LiveUSB Creator''' from [https://fedorahosted.org/liveusb-creator/#Download FedoraHosted here].
# Plug a blank target USB flash drive (or SD Card) into your computer (1GB or greater). (See [http://wiki.sugarlabs.org/go/Category:Live_USB#Cautions_with_using_Live_USB.27s Cautions with using Live USB] regarding flash drive size.)
# Launch LiveUSB Creator.
# Select '''Sugar on a Stick v2 Blueberry''' in the drop-down menu on the upper-right side to download the liveUSB disk image.
# Adjust the Persistent Storage slider. This enables you to save the child's work in Sugar onto the device.
# Select your flash drive as the target and click the '''Create Live USB''' button.
# Wait for the process to finish, then close the LiveUSB Creator program.
# Stop your flash drive using the '''Safely Remove Hardware''' dialog and eject it.
|}

::'''Option #2: (ADVANCED USERS ONLY) Create a bootable Sugar/Blueberry USB flash drive that does not have a compressed filesystem.''' This option requires at least a 4GB drive.

::::'''WARNING: MAKING A MISTAKE IN THIS PROCEDURE COULD WIPE YOUR PC'S HARD DISK!!!!'''

::# In Windows, download the latest version of the [http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso Live CD image], and burn the image to a CD.
::# Follow the instructions [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/ZyX-LiveInstaller here] to create the bootable Sugar/Blueberry USB flash drive by (i) booting the PC into Sugar with the CD and (ii) running ZyX-LiveInstaller within the Terminal activity. You will also need a spare, blank (or erasable) USB flash drive -- preferably manufactured by a different manufacturer than the target USB -- to use as a swap drive during the procedure. Any data on the swap drive will be wiped.

Notes:

* If you do Option #1 often, you may want to download the Blueberry [http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso CD Image] once. Then, when it comes to create the flash drive, hit the Browse button and select the downloaded file rather than selecting "Blueberry" from the menu as above.

* Option #1 creates an SoaS that cannot detect when its drive space eventually runs out, causing stick failure.

* Option #2 creates a more-robust, more-stable drive whose free space can be monitored using the Terminal activity. Non-compressed SoaS drives, however, are not bootable with a boot helper CD.

=== For GNU/Linux Users ===

1-)Linux Users will use a slightly different approach than Windows Users to ensure maximum compatibility
with different distributions. Please follow the instructions carefully to ensure your data is preserved.

If you are a '''Fedora User''', run the following command:

<code>''yum install liveusb-creator''</code>

Then download [http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso soas-2-blueberry.iso] and select it by using the Browse button. You can check to make sure that the .iso downloaded properly by comparing the sha1sum to the one here:[http://download.sugarlabs.org/soas/releases/SHA1SUM](sha1sum)

sha1sum soas-2-blueberry.iso
8022b68433295f12fbfffa66bf49205851a6a1e0

* Launch LiveUSB Creator and follow the instructions [[SoaS_Blueberry_Instructions#For_Windows_Users|above]].

2-)If you use any '''other distribution''', download the '''image-writer''' tool from [http://download.sugarlabs.org/soas/releases/image-writer here] and the '''live image''' from [http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso here].

'''This solution will not create a persistent storage overlay'''

* Open a terminal and become root, either by using su or sudo.
* Enter the following command: ''./image-writer soas-2-blueberry.iso''
* '''WARNING:''' If you proceed here, your flash drive will be wiped!
* The script will output a device name; confirm that it matches with your flash drive.
* You will be notified once the process has finished.

3-)'''zyx-liveinstaller:'''[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/ZyX-LiveInstaller]

4-)Unsupported''' instructions for creating a key with persistent storage for Blueberry:''' [http://wiki.sugarlabs.org/go/Talk:SoaS_Blueberry_Instructions] and on other distributions are available here:[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Linux]

=== For Mac OS X Users ===

The procedure for Mac OS X users is similar to the one for Linux users. Verify that you have an Intel processor, and not a PowerPC (PPC) G3, G4, or G5 processor Apple Macintosh. Mac users should be aware that they may be able to prepare their flash drive on a Mac, but depending on the generation of the hardware used, they may need to use another computer to test whether the prepared flash drive works.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: white;"
|-
|valign=top|[[Image:image-writer-mac.png|left|300px]]
|valign=top|
* Download the '''Sugar on a Stick v2 Blueberry''' liveUSB image from here: http://download.sugarlabs.org/soas/releases/soas-2-blueberry.iso
* You can check if the entire file was downloaded properly by opening the Terminal application and using the '''shasum''' command on the downloaded file: 
shasum ~/Downloads/soas-2-blueberry.iso
8022b68433295f12fbfffa66bf49205851a6a1e0
* Download the '''image-writer''' tool for Macs from here: http://download.sugarlabs.org/soas/releases/image-writer-mac
* Insert a flash drive. '''WARNING:''' your flash drive will be wiped in the next step!
* Execute the following command in Terminal: ''cd Downloads; python image-writer-mac soas-2-blueberry.iso''
* Proceed as stated in the instructions for Linux Users.
|}

=== Boot Helper ===
If your machine doesn't support booting from USB devices, then download the [http://download.sugarlabs.org/soas/releases/soas-2-boot.iso soas-2-boot.iso] and burn it to a CD. [http://www.imgburn.com/ ImgBurn] is a free Windows application to do so, in case your current computer does not come with such a software.

* Use the [[wikipedia:Windows Explorer|Windows Explorer]] to name your USB flash drive FEDORA (from the Properties dialog for your device), as otherwise, it won't be recognized by the boot-helper CD.
* Put both the boot-helper CD and the USB flash drive in your computer and let it boot from the CD.

Find help

2010-03-12T15:24:28Z

David Kergyl: /* Finding answers to help */ Add link to OLPC Support FAQ with explanation.

<noinclude>{{Translations | [[Sugar help|english]] | [[Sugar help/lang-pt|português]] | [[Sugar help/lang-es|español]] | }}
{{TOCright}}</noinclude>

==Finding answers to help==
For general help on Sugar or about Sugar Labs, please see also

'''→''' '''[[Getting Started | Getting started]]'''

'''→''' '''[[Sugar Labs/FAQ | Sugar Labs FAQ]]''' - a compilation of the team FAQs

'''→''' '''[[:Category:FAQ]]''' - an index to all FAQ pages ('''with links for new questions''')

'''→''' '''[[:Category:Help]]''' - pages tagged as 'Help'

'''→''' '''[[:Category:HowTo]]''' - pages tagged as 'HowTo'

'''→''' '''[[Sugar_Labs/Communication channels#Forums|Community Forums]]''' - on-line forums with lots of topics

'''→''' '''[[OLPC:Support FAQ|OLPC's Support FAQ]]''' - FAQs about the XO laptop, its version of Sugar, and Activities. Much information is applicable to the current version of Sugar (e.g., using Activities).

:'''Former sites'''—these have a short history of problems, but are no longer preferred by Sugar Labs.

:: http://getsatisfaction.com/sugarlabs & http://launchpad.net/soas

===The Sugar Learners' manual===
{| class="wikitable"
|-
| [http://flossmanuals.net/Sugar http://wiki.sugarlabs.org/images/4/40/Sugarlabs_mainpage_07.png]
|available as: [http://en.flossmanuals.net/Sugar HTML] or [{{FlossmanualPDF}} .pdf] 128 pages, 8.3 MBytes (for saving or printing).
|}
===Sugar [[Glossary|glossary]]===
: There is a [[Glossary|glossary with commonly used acronyms available here]].

{{:Tutorials}}

===[[The Undiscoverable]]===

: We have tried hard to make it easy for children to [[Discovery|discover]] what they can do with Sugar software without being told. But that isn't always possible. So we have a list of things that teachers should know about, and be able to demonstrate. If you find some feature of the software incomprehensible, please add it to the list, and we will see what we can do for you and everybody else who runs into the same problem. Sometimes the answer is a click of the mouse away, but not always. We are, after all, introducing children to all of human knowledge. They will inevitably need help with much of it. It took all of our ancestors many years to get this far, so it is alright if children spend a few years hitting the highlights, and getting help to do it.

----

===OLPC Project Help and Information===
: For general help and information about the OLPC Project, please see these links at the [[olpc:The OLPC Wiki|The OLPC Wiki]]:
: [[OLPC:Official OLPC FAQ | Official OLPC FAQ]], [[OLPC:Support FAQ|Support FAQ]], for questions about the XO laptop and its use, [[OLPC:Support|Support]], for more support mechanisms, [[OLPC::Category:OLPC FAQ|:Category:OLPC FAQ]], and [[OLPC:Ask OLPC a Question | Ask OLPC a Question]] (in roughly that order).
----
===[[Request_New_Features| Request new features]]===
: Please use our [[Request_New_Features|Request New Features page]].
: If you can't find your answer, please request one or ''supply one!'' below:

== Help Requests:==
:Click on an '''[edit]''' link next to a topic paragraph below to enter your request or an answer (you will see more instructions on the edit form). '''But first''', if possible, login or register on the wiki, leave an email address (secured by your login password), and then you can choose to 'Watch' any page on the wiki (such as this one) by clicking the 'Watch tab', and you will receive an email if the page changes. Plus, others can respond to you privately by using the 'E-mail this user' link in the sidebar of your user page.

:There are also links for new questions on the [[:Category:FAQ]] pages.
===on Usage ===
:First, see the help links above.

* 

* I would like to install [[olpc:Adobe Flash|Adobe Flash]] Player in order to access the learn-to-read website www.starfall.com with Browser. (i) Can the Sugar Browser run the Adobe Flash Player plug-in? (ii) If so, please modify the YUM instructions from Adobe (copied below) as needed for the Sugar environment. I'm a Windows user, so please include all necessary Terminal instructions (e.g., to change to the correct directory). Thanks in advance.
*: Installation instructions for the YUM repository definition
*:# Click the download link to begin installation. A dialog box will appear asking you where to save the file.
*:# Save the .rpm file to your desktop and wait for the file to download completely.
*:# In terminal, navigate to the desktop and type # rpm -Uvh <rpm_package_file>. Click Enter. (Note: This must be done as a root user).
*:# Once the installation is complete, in terminal, type # yum install flash-plugin. Click Enter. (Note: This must be done as a root user).
*:# To verify the plugin is installed in Mozilla, launch Mozilla and choose Help > About Plug-ins from the browser menu.
*:: (See http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-3.) - [[User:David Kergyl|David Kergyl]] 23:14, 10 March 2010 (UTC)

===on [[Wiki_Team/Resources | the Wiki]] ===
:First, see the [[Wiki Team/Resources]] page.

* 

===on Submitting a bug===
:Please report problems or bugs on '''[[Submit_Bugs/Problems| Submit Bugs/Problems page]]'''.

* 

===on Releases===
:First, see this page, [[{{Upcoming Stable Release}}/Roadmap]].

* 

===on Distributions===
:First, see the '''[[Downloads]]''' and '''[[Supported systems]]''' pages.

* 

* Live CD in Spanish
*:Purport: I see as one of the selling points of Sugar that a non-expert user can use computers "off the bat". It has been reported to me that currently the LiveCD requires some tweaking at startup to adjust it to a given locale, which I feel is to ask too much precisely from users that are not skilled. Goal: a LiveCD version that is localized in Spanish from startup, with no tweaking required, to be distributable among the Spanish-speaking public.
*::Contact: yamaplos at bolinux.org

=== on Sugar hardware ports===
:First, see the '''[[Supported systems]]''' page.

* 

=== on Sugar activities===
:First, see the [[Activity Team]] pages.

* 

* According to this review, [[olpc:Scratch|Scratch]] requires some setup in Terminal:
*: ... Scratch lacks Sugar integration but it does have the benefit that you can store and retrieve Scratch in file folders which the user can setup. Unfortunately this does require some help with setting up files under Linux and giving the user write permission on those files. The plus side of all of this is that the user can read and write to a USB memory stick and share Scratch files with Scratch on other computers.... Rated 4 out of 5 stars by Bill on February 28, 2010
*:: Is this correct? Is such setup also required to use the Scratch included on the Blueberry SoaS? If so, please add a wiki section containing specific instructions for performing this setup in Terminal. The Scratch activities page should also link to the instructions. - [[User:David Kergyl|David Kergyl]] 16:36, 11 March 2010 (UTC)
*::: '''Thank you''' David for you contributions to the wiki both here and elsewhere! While you have entered your questions at appropriate places in the wiki for their future reference, if you accompany your question with a post to either of these [[Sugar Labs/Communication channels#Mailing Lists|mailing lists]], [http://lists.sugarlabs.org/listinfo/iaep It's An Education Project, IAEP] (for general), or [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] (for development-related) discussions, you will reach many more Sugar Labs followers who are not currently following changes on this wiki. We can then reference the discussion thread in the wiki and also provide a consolidated summary. --[[User:FGrose|FGrose]] 17:25, 11 March 2010 (UTC)

=== on Sugar deployments===
:First, see the [[Deployment Team]] pages.

* 

=== on Sugar Labs===
: See the '''[[Sugar Labs]]''' page. Sugar Labs was created to provide a mechanism for supporting the Sugar community of volunteers. These volunteers are engaged in a variety of activities: some are writing software to improve Sugar; some are porting Sugar to new platforms; some are developing new activities that run in Sugar; some are helping to debug Sugar and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios for learning with Sugar; some are using Sugar and reporting upon their experiences to the community; and some are providing help and support.

:Since we started Sugar Labs, we have been receiving a number of requests for help: porting Sugar to new distributions; tuning Sugar on a specific hardware platform; developing specific Sugar activity; helping with support in specific deployments, etc. Please use this page both to make requests and respond to requests for help.

* 

[[Category:General public]]
[[Category:Help]]

User:David Kergyl

2010-03-11T19:56:21Z

David Kergyl: Created page with 'New user; very impressed by the platform.'

New user; very impressed by the platform.

User talk:FGrose

2010-03-11T19:55:02Z

David Kergyl: /* Adobe Flash Player (AFP) */ new section

Tutorials

2010-03-11T19:47:48Z

David Kergyl: /* Tutorials */ Corrected last change.

===Tutorials===
* Ideas for [[How to present Sugar]].
* Tech Coordinator Guide and other [http://olpcnyc.wordpress.com/training-materials/ training materials] prepared by Teaching Matters(R) for OLPC in NYC
====Videos====
{{:Video Using Sugar}}

====Developer mini tutorials====
* See [[Development Team/Mini tutorials]].

[[Category:HowTo]]

Tutorials

2010-03-11T19:47:11Z

David Kergyl: /* Tutorials */ Added link to OLPC in NYC.

===Tutorials===
* Ideas for [[How to present Sugar]].
* Tech Coordinator Guide and other [http://olpcnyc.wordpress.com/training-materials/ training materials] prepared by Teaching Matters(R) for OLPC in NYC http://olpcnyc.wordpress.com/training-materials/
====Videos====
{{:Video Using Sugar}}

====Developer mini tutorials====
* See [[Development Team/Mini tutorials]].

[[Category:HowTo]]

Sugar on a Stick/TODO

2010-03-11T17:55:29Z

David Kergyl: /* Using a CD helper takes a lot of prep time before and after class */ Propose network boot helper.

<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792}}
[[Category:TODO]]</noinclude>

==Sugar on a Stick Improve Deployability==

The good news is Sugar on a Stick is being successfully used in Schools around the world now! Based on these experiences this is a list of some of the known challenges that people may face piloting Sugar on a Stick right now. September is start of school in the US, so we expect to see an increase in teachers trying Sugar. We want to be ready with suggestions and work arounds as people face these challenges.

===Make it easier for a teacher or school to customize a spin and then copy it for a hundred kids===

Tickets on this topic:

Red Hat - http://bugzilla.redhat.com/show_bug.cgi?id=448030 - RFE: create a bootable Live USB stick from the running livecd, also Sugar Labs Ticket {{Bug|74}}.

''Use Case''
A teacher should be able to create a USB stick, add activities, add some content, change the language, change the jabber server etc. Then create new sticks that reflect these changes but do not copy the name, color or collaboration key.

It would be great if the teacher could use an inexpensive USB hub to burn more then one stick at a time.

===Stick Failure===

Discussions of Stick Failure and alternative file structures is now at [[../Stick Layout]]

===Backup and recovery===

Ham and Dave from Solution Grove are making progress on this. You can track progress on ticket {{bug|916}}

===What is a reasonable expectation for the role of the XS in Sugar on a Stick deployments in the next 6 months?===
===Collaboration is unreliable and thus frustrating===
Its working fairly well in the wired network at the GPA lab, but no other use case seem to work reliably. We need to expand the Poets Guide to [[Collaboration]] to give people hints on how to set up a scenario that will work for them.

===Using a CD helper takes a lot of prep time before and after class===
A floppy helper would reduce it. A VM solution might also reduce it. A network boot helper would also reduce it, for PCs that support a network boot.

'''Tickets'''
* Ticket {{Bug|598}} - Boot Helper Virtual Machine
* Ticket {{Bug|907}} - change the format we use for the USB stick
* Ticket {{Bug|597}} - Floppy disc Boot Helper

See also [[Sugar on a Stick/Goals]].

* [[Gardner Pilot Academy#Critical Path Technical Issues]]

{{Transclude|To do to improve Sugar on a Stick}}

Find help

2010-03-11T16:39:55Z

David Kergyl: /* on Sugar activities */

<noinclude>{{Translations | [[Sugar help|english]] | [[Sugar help/lang-pt|português]] | [[Sugar help/lang-es|español]] | }}
{{TOCright}}</noinclude>

==Finding answers to help==
For general help on Sugar or about Sugar Labs, please see also

'''→''' '''[[Getting Started | Getting started]]'''

'''→''' '''[[Sugar Labs/FAQ | Sugar Labs FAQ]]''' - a compilation of the team FAQs

'''→''' '''[[:Category:FAQ]]''' - an index to all FAQ pages ('''with links for new questions''')

'''→''' '''[[:Category:Help]]''' - pages tagged as 'Help'

'''→''' '''[[:Category:HowTo]]''' - pages tagged as 'HowTo'

'''→''' '''[[Sugar_Labs/Communication channels#Forums|Community Forums]]''' - on-line forums with lots of topics
:'''Former sites'''—these have a short history of problems, but are no longer preferred by Sugar Labs.

:: http://getsatisfaction.com/sugarlabs & http://launchpad.net/soas

===The Sugar Learners' manual===
{| class="wikitable"
|-
| [http://flossmanuals.net/Sugar http://wiki.sugarlabs.org/images/4/40/Sugarlabs_mainpage_07.png]
|available as: [http://en.flossmanuals.net/Sugar HTML] or [{{FlossmanualPDF}} .pdf] 128 pages, 8.3 MBytes (for saving or printing).
|}
===Sugar [[Glossary|glossary]]===
: There is a [[Glossary|glossary with commonly used acronyms available here]].

{{:Tutorials}}

===[[The Undiscoverable]]===

: We have tried hard to make it easy for children to [[Discovery|discover]] what they can do with Sugar software without being told. But that isn't always possible. So we have a list of things that teachers should know about, and be able to demonstrate. If you find some feature of the software incomprehensible, please add it to the list, and we will see what we can do for you and everybody else who runs into the same problem. Sometimes the answer is a click of the mouse away, but not always. We are, after all, introducing children to all of human knowledge. They will inevitably need help with much of it. It took all of our ancestors many years to get this far, so it is alright if children spend a few years hitting the highlights, and getting help to do it.

----

===OLPC Project Help and Information===
: For general help and information about the OLPC Project, please see these links at the [[olpc:The OLPC Wiki|The OLPC Wiki]]:
: [[OLPC:Official OLPC FAQ | Official OLPC FAQ]], [[OLPC:Support FAQ|Support FAQ]], for questions about the XO laptop and its use, [[OLPC:Support|Support]], for more support mechanisms, [[OLPC::Category:OLPC FAQ|:Category:OLPC FAQ]], and [[OLPC:Ask OLPC a Question | Ask OLPC a Question]] (in roughly that order).
----
===[[Request_New_Features| Request new features]]===
: Please use our [[Request_New_Features|Request New Features page]].
: If you can't find your answer, please request one or ''supply one!'' below:

== Help Requests:==
:Click on an '''[edit]''' link next to a topic paragraph below to enter your request or an answer (you will see more instructions on the edit form). '''But first''', if possible, login or register on the wiki, leave an email address (secured by your login password), and then you can choose to 'Watch' any page on the wiki (such as this one) by clicking the 'Watch tab', and you will receive an email if the page changes. Plus, others can respond to you privately by using the 'E-mail this user' link in the sidebar of your user page.

:There are also links for new questions on the [[:Category:FAQ]] pages.
===on Usage ===
:First, see the help links above.

* 

* I would like to install Adobe Flash Player in order to access the learn-to-read website www.starfall.com with Browser. (i) Can the Sugar Browser run the Adobe Flash Player plug-in? (ii) If so, please modify the YUM instructions from Adobe (copied below) as needed for the Sugar environment. I'm a Windows user, so please include all necessary Terminal instructions (e.g., to change to the correct directory). Thanks in advance.

:::Installation instructions for the YUM repository definition
::: 1. Click the download link to begin installation. A dialog box will appear asking you where to save the file.
::: 2. Save the .rpm file to your desktop and wait for the file to download completely.
::: 3. In terminal, navigate to the desktop and type # rpm -Uvh <rpm_package_file>. Click Enter. (Note: This must be done as a root user).
::: 4. Once the installation is complete, in terminal, type # yum install flash-plugin. Click Enter. (Note: This must be done as a root user).
::: 5. To verify the plugin is installed in Mozilla, launch Mozilla and choose Help > About Plug-ins from the browser menu.

(See http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-3.)
[[User:David Kergyl|David Kergyl]] 23:14, 10 March 2010 (UTC)

===on [[Wiki_Team/Resources | the Wiki]] ===
:First, see the [[Wiki Team/Resources]] page.

* 

===on Submitting a bug===
:Please report problems or bugs on '''[[Submit_Bugs/Problems| Submit Bugs/Problems page]]'''.

* 

===on Releases===
:First, see this page, [[{{Upcoming Stable Release}}/Roadmap]].

* 

===on Distributions===
:First, see the '''[[Downloads]]''' and '''[[Supported systems]]''' pages.

* 

* Live CD in Spanish
*:Purport: I see as one of the selling points of Sugar that a non-expert user can use computers "off the bat". It has been reported to me that currently the LiveCD requires some tweaking at startup to adjust it to a given locale, which I feel is to ask too much precisely from users that are not skilled. Goal: a LiveCD version that is localized in Spanish from startup, with no tweaking required, to be distributable among the Spanish-speaking public.
*::Contact: yamaplos at bolinux.org

=== on Sugar hardware ports===
:First, see the '''[[Supported systems]]''' page.

* 

=== on Sugar activities===
:First, see the [[Activity Team]] pages.

* 

* According to this review, Scratch requires some setup in Terminal:
:::... Scratch lacks Sugar integration but it does have the benefit that you can store and retrieve Scratch in file folders which the user can setup. Unfortunately this does require some help with setting up files under Linux and giving the user write permission on those files. The plus side of all of this is that the user can read and write to a USB memory stick and share Scratch files with Scratch on other computers.... Rated 4 out of 5 stars by Bill on February 28, 2010

Is this correct? Is such setup also required to use the Scratch included on the Blueberry SoaS? If so, please add a wiki section containing specific instructions for performing this setup in Terminal. The Scratch activities page should also link to the instructions.
[[User:David Kergyl|David Kergyl]] 16:36, 11 March 2010 (UTC)

=== on Sugar deployments===
:First, see the [[Deployment Team]] pages.

* 

=== on Sugar Labs===
: See the '''[[Sugar Labs]]''' page. Sugar Labs was created to provide a mechanism for supporting the Sugar community of volunteers. These volunteers are engaged in a variety of activities: some are writing software to improve Sugar; some are porting Sugar to new platforms; some are developing new activities that run in Sugar; some are helping to debug Sugar and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios for learning with Sugar; some are using Sugar and reporting upon their experiences to the community; and some are providing help and support.

:Since we started Sugar Labs, we have been receiving a number of requests for help: porting Sugar to new distributions; tuning Sugar on a specific hardware platform; developing specific Sugar activity; helping with support in specific deployments, etc. Please use this page both to make requests and respond to requests for help.

* 

[[Category:General public]]
[[Category:Help]]

Find help

2010-03-11T16:36:19Z

David Kergyl: /* on Sugar activities */ Add help request regarding Scratch setup.

<noinclude>{{Translations | [[Sugar help|english]] | [[Sugar help/lang-pt|português]] | [[Sugar help/lang-es|español]] | }}
{{TOCright}}</noinclude>

==Finding answers to help==
For general help on Sugar or about Sugar Labs, please see also

'''→''' '''[[Getting Started | Getting started]]'''

'''→''' '''[[Sugar Labs/FAQ | Sugar Labs FAQ]]''' - a compilation of the team FAQs

'''→''' '''[[:Category:FAQ]]''' - an index to all FAQ pages ('''with links for new questions''')

'''→''' '''[[:Category:Help]]''' - pages tagged as 'Help'

'''→''' '''[[:Category:HowTo]]''' - pages tagged as 'HowTo'

'''→''' '''[[Sugar_Labs/Communication channels#Forums|Community Forums]]''' - on-line forums with lots of topics
:'''Former sites'''—these have a short history of problems, but are no longer preferred by Sugar Labs.

:: http://getsatisfaction.com/sugarlabs & http://launchpad.net/soas

===The Sugar Learners' manual===
{| class="wikitable"
|-
| [http://flossmanuals.net/Sugar http://wiki.sugarlabs.org/images/4/40/Sugarlabs_mainpage_07.png]
|available as: [http://en.flossmanuals.net/Sugar HTML] or [{{FlossmanualPDF}} .pdf] 128 pages, 8.3 MBytes (for saving or printing).
|}
===Sugar [[Glossary|glossary]]===
: There is a [[Glossary|glossary with commonly used acronyms available here]].

{{:Tutorials}}

===[[The Undiscoverable]]===

: We have tried hard to make it easy for children to [[Discovery|discover]] what they can do with Sugar software without being told. But that isn't always possible. So we have a list of things that teachers should know about, and be able to demonstrate. If you find some feature of the software incomprehensible, please add it to the list, and we will see what we can do for you and everybody else who runs into the same problem. Sometimes the answer is a click of the mouse away, but not always. We are, after all, introducing children to all of human knowledge. They will inevitably need help with much of it. It took all of our ancestors many years to get this far, so it is alright if children spend a few years hitting the highlights, and getting help to do it.

----

===OLPC Project Help and Information===
: For general help and information about the OLPC Project, please see these links at the [[olpc:The OLPC Wiki|The OLPC Wiki]]:
: [[OLPC:Official OLPC FAQ | Official OLPC FAQ]], [[OLPC:Support FAQ|Support FAQ]], for questions about the XO laptop and its use, [[OLPC:Support|Support]], for more support mechanisms, [[OLPC::Category:OLPC FAQ|:Category:OLPC FAQ]], and [[OLPC:Ask OLPC a Question | Ask OLPC a Question]] (in roughly that order).
----
===[[Request_New_Features| Request new features]]===
: Please use our [[Request_New_Features|Request New Features page]].
: If you can't find your answer, please request one or ''supply one!'' below:

== Help Requests:==
:Click on an '''[edit]''' link next to a topic paragraph below to enter your request or an answer (you will see more instructions on the edit form). '''But first''', if possible, login or register on the wiki, leave an email address (secured by your login password), and then you can choose to 'Watch' any page on the wiki (such as this one) by clicking the 'Watch tab', and you will receive an email if the page changes. Plus, others can respond to you privately by using the 'E-mail this user' link in the sidebar of your user page.

:There are also links for new questions on the [[:Category:FAQ]] pages.
===on Usage ===
:First, see the help links above.

* 

* I would like to install Adobe Flash Player in order to access the learn-to-read website www.starfall.com with Browser. (i) Can the Sugar Browser run the Adobe Flash Player plug-in? (ii) If so, please modify the YUM instructions from Adobe (copied below) as needed for the Sugar environment. I'm a Windows user, so please include all necessary Terminal instructions (e.g., to change to the correct directory). Thanks in advance.

:::Installation instructions for the YUM repository definition
::: 1. Click the download link to begin installation. A dialog box will appear asking you where to save the file.
::: 2. Save the .rpm file to your desktop and wait for the file to download completely.
::: 3. In terminal, navigate to the desktop and type # rpm -Uvh <rpm_package_file>. Click Enter. (Note: This must be done as a root user).
::: 4. Once the installation is complete, in terminal, type # yum install flash-plugin. Click Enter. (Note: This must be done as a root user).
::: 5. To verify the plugin is installed in Mozilla, launch Mozilla and choose Help > About Plug-ins from the browser menu.

(See http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-3.)
[[User:David Kergyl|David Kergyl]] 23:14, 10 March 2010 (UTC)

===on [[Wiki_Team/Resources | the Wiki]] ===
:First, see the [[Wiki Team/Resources]] page.

* 

===on Submitting a bug===
:Please report problems or bugs on '''[[Submit_Bugs/Problems| Submit Bugs/Problems page]]'''.

* 

===on Releases===
:First, see this page, [[{{Upcoming Stable Release}}/Roadmap]].

* 

===on Distributions===
:First, see the '''[[Downloads]]''' and '''[[Supported systems]]''' pages.

* 

* Live CD in Spanish
*:Purport: I see as one of the selling points of Sugar that a non-expert user can use computers "off the bat". It has been reported to me that currently the LiveCD requires some tweaking at startup to adjust it to a given locale, which I feel is to ask too much precisely from users that are not skilled. Goal: a LiveCD version that is localized in Spanish from startup, with no tweaking required, to be distributable among the Spanish-speaking public.
*::Contact: yamaplos at bolinux.org

=== on Sugar hardware ports===
:First, see the '''[[Supported systems]]''' page.

* 

=== on Sugar activities===
:First, see the [[Activity Team]] pages.

* 

* According to this review, Scratch requires some setup in Terminal:
:::... Scratch lacks Sugar integration but it does have the benefit that you can store and retrieve Scratch in file folders which the user can setup. Unfortunately this does require some help with setting up files under Linux and giving the user write permission on those files. The plus side of all of this is that the user can read and write to a USB memory stick and share Scratch files with Scratch on other computers.... Rated 4 out of 5 stars by Bill on February 28, 2010

Is this correct? Is such setup also required to use the Scratch included on the Blueberry SoaS? If so, please add a wiki section containing specific instructions for performing this setup in Terminal on a wiki page. The Scratch activities page should also link to the instructions.
[[User:David Kergyl|David Kergyl]] 16:36, 11 March 2010 (UTC)

=== on Sugar deployments===
:First, see the [[Deployment Team]] pages.

* 

=== on Sugar Labs===
: See the '''[[Sugar Labs]]''' page. Sugar Labs was created to provide a mechanism for supporting the Sugar community of volunteers. These volunteers are engaged in a variety of activities: some are writing software to improve Sugar; some are porting Sugar to new platforms; some are developing new activities that run in Sugar; some are helping to debug Sugar and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios for learning with Sugar; some are using Sugar and reporting upon their experiences to the community; and some are providing help and support.

:Since we started Sugar Labs, we have been receiving a number of requests for help: porting Sugar to new distributions; tuning Sugar on a specific hardware platform; developing specific Sugar activity; helping with support in specific deployments, etc. Please use this page both to make requests and respond to requests for help.

* 

[[Category:General public]]
[[Category:Help]]

Marketing Team/Presentations

2010-03-11T15:02:11Z

David Kergyl: /* Presentations on Logo Like Languages */ Add link to Creative Computer Exploration with Scratch

{{TOCright}}
{{Dated}}
== Sugar Labs bullet points ==

* [[How to present Sugar]]
* [[:Image:Sugarlabs-onepager.odp|A one-slide overview]] of Sugar Labs
* [[:Image:Sugarlabs-bullets.odp]]

== Presentations on Logo Like Languages ==
The visual programming languages [http://activities.sugarlabs.org/en-US/sugar/addon/4027 Turtle Art], Scratch and [http://activities.sugarlabs.org/en-US/sugar/addon/4030 Etoys] can be described as "Logo like" in that they are accessable to young kids, are used to promote problem solving and can produce geometric pen trails from programmable turtles (or cats or cars). They are superior to Logo in that they are visual languages rather than text based which allows kids to spend their time in higher order problem solving rather than syntax. Following are presentations which support the educational use of Logo like or visual programming languages.

*[http://www.papert.org/works.html Works by Seymour Papert, Ph.D. (Logo)]
*[http://neoparaiso.com/logo/estudio-logo.html Estudio sobre Logo: Efectos y Eficacia]
*[http://www.vpri.org/html/writings.php Teaching and Learning Powerful Ideas Viewpoint Research Institute (Etoys)]
*[http://scalablegamedesign.cs.colorado.edu/wiki/Scalable_Game_Design_wiki Scalable Game Design wiki (Agentsheets)]
*[http://llk.media.mit.edu/papers/IDC-2005.pdf Some Reflections on designing construction kits for kids, Resnick&Silverman (Scratch)]
*[http://waveplace.org/about/background/ Waveplace Background (Etoys/OLPC]
*[http://rupert.id.au/schoolgamemaker/why.htm Why Games at School?]
*[http://www.ncsu.edu/meridian/jan98/feat_1/kiddesigner.html Project Kid Designer]
*[http://tonyforster.blogspot.com/2009/12/computer-programming-and-acquisition-of.html Computer programming and the acquisition of critical literacy]
*[http://learningevolves.wikispaces.com/file/view/Game+programming%2C+the+Computer+Game+Design%2C.ppt Game programming, the computer game design, programming, multimedia and mathematics cluster]
*[http://www.box.net/public/gaptkprrjs Learning and teaching in the contexts of creating computer games, Holkner 2006]
*[http://www.obscure.org/scratch Creative Computer Exploration with Scratch], a set of lesson plans to teach elementary school children programming, design, and math in an accessible and engaging way (The Obsure Organization)

== Previous events ==
=== 2010 ===

* [http://docs.google.com/present/edit?id=0AaE4gRWaGNm1ZHFyaDNqcl8xOWNjeDV4eGg2&hl=en OLPC/Sugarlabs overview and workshop on hacking activity layouts] - [http://wiki.sugarlabs.org/go/User:Tabitha LCA2010], presentation by [http://wiki.sugarlabs.org/go/User:Tabitha Tabitha Roder] and [http://wiki.laptop.org/go/User:Aly Alastair Munro], [http://wiki.laptop.org/go/OLPC_New_Zealand New Zealand volunteers]; [http://wiki.sugarlabs.org/go/User:Tabitha/Events/LCA2010 Event page]

* [[Media:SugarIgalia.odp|Sugar: pasado, presente y futuro]] by [[User:Tomeu|Tomeu]]

* [[Media:SugarLabs_LAtelierBNPParibas.rev01.pdf|Presentation at OLPC event Feb. 3, 2010 at L'Atelier BNP Paribas, Paris]] by [[User:SeanDaly|Sean]]

* [http://people.sugarlabs.org/bernie/sugar/slides/sugar-paraguay-v6-es.odp Empoderar a los estudiantes con el software libre (ODP)], [http://people.sugarlabs.org/bernie/sugar/slides/sugar-paraguay-v6-es.pdf PDF], presented by [[User:Bernie|Bernie]] on March 2 2010 at the [http://www.pol.una.py/ Facultad Politecnica de la Universidad Nacional de Asuncion], Paraguay.

* [http://people.sugarlabs.org/bernie/sugar/slides/sugar-paraguay-v5-en.odp Empowering Students with Free Software], older version of the above in English, with fewer slides and a few factual errors.

===2009===

* [http://wiki.laptop.org/images/d/d6/BozLUGTiny.pdf OLPC / Sugar Labs overview presentation]

====NECC====
* [[File:NECCunplugged-Bender.pdf]]

====FOSSVT====
* [[Image:FOSSVT.xol]]

====CoSN (Consortium for School Networking) 2009 Annual Conference, Austin, TX====
'''12 March 2009'''
* [[Media:Sugar_User-Interface_Opportunity.pdf | Sugar User Interface Opportunity]], Anne Gentle presenting on behalf of Walter Bender.

====CUE (Computer Using Educators)Conference, Palm Springs CA====
'''March 2009'''
* [[olpc:Image:CUE_XO_03-05-09.pdf | One Laptop Per Child: What's The Fuss All About?]], Caryl Bigenho's overview of OLPC, the XO, and Sugar for Califonia Educators. Ppt version to follow.

==== FOSDEM 2009 ====

* [[Media:FOSDEM2009.odp|The Sugar platform: Why GNOME may care?]] by Tomeu Vizoso

===2008===

* [[:Image:Netbook.odp| Walter's Netbook World Summit talk]]

* [http://stud4.tuwien.ac.at/~e0425826/FUDCon.odp FUDCon 2008 Brno] (Christoph Derndorfer)

* [http://www.codewiz.org/pub/sugar/slides/SugarBeagle.odp ESC Boston 2008] ([[User:Bernie|Bernie Innocenti]])

* [http://www.codewiz.org/pub/sugar/slides/ Bernie's collection of OLPC & Sugar marketing material]

* [[:Image:Bolzano.odp| Walter's talk in Bolzano, Italy]]

* [[:Image:USMP.odp|Walter's talk at the University of San Martin de Porres, Lima Peru]]

=== 2008 SugarCamp ===

Video for many of these is available in raw form at http://download.laptop.org/content/conf/20081117-sugarcamp/ -- help is welcome in editing & converting to free formats!

John Tierney was so nice to share with us the mind maps he took while attending the talks: [[Image:SugarCamp_Mind_Map_Collection.pdf]].

=== Monday ===

* [http://www.codewiz.org/pub/olpc/slides/sugarcamp/SugarcampIntro.odp Sugarcamp intro] ([[User:Bernie|Bernie Innocenti]])

=== Tuesday ===

* [http://people.collabora.co.uk/~cassidy/talks/sugar-camp-collab-archi-and-state-of-implementation.pdf Collaboration state of the art] (Guillaume Desmottes)

* [http://people.collabora.co.uk/~cassidy/talks/sugar-camp-futur-of-collab.pdf Future of collaboration] (Guillaume Desmottes)

* [http://docs.google.com/EmbedSlideshow?docid=dcfrb5jw_1dqrh9sgr The medium is the message] (Yama)

=== Wednesday ===

* [[Media:Sugarcamp-cscott-legacy.pdf | Desktop legacy compatibility]] ([[User:CScott|CScott]])
* [[Media:I18n.pdf | Internationalization]] (Sayamindu)
* [http://dev.laptop.org/git?p=users/cscott/talks;a=blob_plain;f=sugarcamp-i18n.pdf;hb=HEAD Internationalization] ([[User:CScott|CScott]])
* [http://dev.laptop.org/git?p=users/cscott/talks;a=blob_plain;f=sugarcamp-misc.pdf;hb=HEAD Misc. Topics] ([[User:CScott|CScott]])
* [Media:Sugarcamp-cscott-network.pdf | Network]] ([[User:CScott|CScott]])

=== Thursday ===

* [[Media:Sugar-meeting.odp|working with users Open Office presentation by Greg Smith]]
* [http://www.resara.com/presentation.ppt Resara and LTSP by Brendan Powers] (PowerPoint — [http://docs.google.com/Presentation?id=dcvvrqtp_241fjp7rdgm view in Google Docs])
* [http://docs.google.com/Presentation?id=dddknwgs_360gwgwbnf2 Caroline Meeks - Sugar on a Stick]
* [http://dev.laptop.org/git?p=users/cscott/talks;a=blob_plain;f=sugarcamp-collab.pdf;hb=HEAD Collaboration] ([[User:CScott|CScott]])

=== Friday ===

* [[Media:Portfolios.odp|Sugar portfolios presentation by Walter Bender and Evangeline Harris Stefanakis]]
* [[Media:SugarLabsOverview.odp|Sugar Labs overview by Walter Bender]]
* [http://www.christianmarcschmidt.com/components/schmidt_sugar_design.pdf Design Opportunities for Sugar, by Christian Marc Schmidt and Eben Eliason]

=== Saturday ===
* [http://www.codewiz.org/pub/sugar/slides/sugarcamp/SugarLabsInfrastructure.odp Sugar Labs infrastructure] ([[User:Bernie|Bernie Innocenti]])

Find help

2010-03-10T23:14:09Z

David Kergyl: /* on Usage */ Add request for installation help for Adobe Flash Player

<noinclude>{{Translations | [[Sugar help|english]] | [[Sugar help/lang-pt|português]] | [[Sugar help/lang-es|español]] | }}
{{TOCright}}</noinclude>

==Finding answers to help==
For general help on Sugar or about Sugar Labs, please see also

'''→''' '''[[Getting Started | Getting started]]'''

'''→''' '''[[Sugar Labs/FAQ | Sugar Labs FAQ]]''' - a compilation of the team FAQs

'''→''' '''[[:Category:FAQ]]''' - an index to all FAQ pages ('''with links for new questions''')

'''→''' '''[[:Category:Help]]''' - pages tagged as 'Help'

'''→''' '''[[:Category:HowTo]]''' - pages tagged as 'HowTo'

'''→''' '''[[Sugar_Labs/Contacts#Forums|Community Forums]]''' - on-line forums with lots of topics
:'''Former sites'''—these have a short history of problems, but are no longer preferred by Sugar Labs.

:: http://getsatisfaction.com/sugarlabs & http://launchpad.net/soas

===The Sugar Learners' manual===
{| class="wikitable"
|-
| [http://flossmanuals.net/Sugar http://wiki.sugarlabs.org/images/4/40/Sugarlabs_mainpage_07.png]
|available as: [http://en.flossmanuals.net/Sugar HTML] or [{{FlossmanualPDF}} .pdf] 128 pages, 8.3 MBytes (for saving or printing).
|}
===Sugar [[Glossary|glossary]]===
: There is a [[Glossary|glossary with commonly used acronyms available here]].

{{:Tutorials}}

===[[The Undiscoverable]]===

: We have tried hard to make it easy for children to [[Discovery|discover]] what they can do with Sugar software without being told. But that isn't always possible. So we have a list of things that teachers should know about, and be able to demonstrate. If you find some feature of the software incomprehensible, please add it to the list, and we will see what we can do for you and everybody else who runs into the same problem. Sometimes the answer is a click of the mouse away, but not always. We are, after all, introducing children to all of human knowledge. They will inevitably need help with much of it. It took all of our ancestors many years to get this far, so it is alright if children spend a few years hitting the highlights, and getting help to do it.

----

===OLPC Project Help and Information===
: For general help and information about the OLPC Project, please see these links at the [[olpc:The OLPC Wiki|The OLPC Wiki]]:
: [[OLPC:Official OLPC FAQ | Official OLPC FAQ]], [[OLPC:Support FAQ|Support FAQ]], for questions about the XO laptop and its use, [[OLPC:Support|Support]], for more support mechanisms, [[OLPC::Category:OLPC FAQ|:Category:OLPC FAQ]], and [[OLPC:Ask OLPC a Question | Ask OLPC a Question]] (in roughly that order).
----
===[[Request_New_Features| Request new features]]===
: Please use our [[Request_New_Features|Request New Features page]].
: If you can't find your answer, please request one or ''supply one!'' below:

== Help Requests:==
:Click on an '''[edit]''' link next to a topic paragraph below to enter your request or an answer (you will see more instructions on the edit form). '''But first''', if possible, login or register on the wiki, leave an email address (secured by your login password), and then you can choose to 'Watch' any page on the wiki (such as this one) by clicking the 'Watch tab', and you will receive an email if the page changes. Plus, others can respond to you privately by using the 'E-mail this user' link in the sidebar of your user page.

:There are also links for new questions on the [[:Category:FAQ]] pages.
===on Usage ===
:First, see the help links above.

* 

* I would like to install Adobe Flash Player in order to access the learn-to-read website www.starfall.com with Browser. (i) Can the Sugar Browser run the Adobe Flash Player plug-in? (ii) If so, please modify the YUM instructions from Adobe (copied below) as needed for the Sugar environment. I'm a Windows user, so please include all necessary Terminal instructions (e.g., to change to the correct directory). Thanks in advance.

:::Installation instructions for the YUM repository definition
::: 1. Click the download link to begin installation. A dialog box will appear asking you where to save the file.
::: 2. Save the .rpm file to your desktop and wait for the file to download completely.
::: 3. In terminal, navigate to the desktop and type # rpm -Uvh <rpm_package_file>. Click Enter. (Note: This must be done as a root user).
::: 4. Once the installation is complete, in terminal, type # yum install flash-plugin. Click Enter. (Note: This must be done as a root user).
::: 5. To verify the plugin is installed in Mozilla, launch Mozilla and choose Help > About Plug-ins from the browser menu.

(See http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-3.)
[[User:David Kergyl|David Kergyl]] 23:14, 10 March 2010 (UTC)

===on [[Wiki_Team/Resources | the Wiki]] ===
:First, see the [[Wiki Team/Resources]] page.

* 

===on Submitting a bug===
:Please report problems or bugs on '''[[Submit_Bugs/Problems| Submit Bugs/Problems page]]'''.

* 

===on Releases===
:First, see this page, [[{{Upcoming Stable Release}}/Roadmap]].

* 

===on Distributions===
:First, see the '''[[Downloads]]''' and '''[[Supported systems]]''' pages.

* 

* Live CD in Spanish
*:Purport: I see as one of the selling points of Sugar that a non-expert user can use computers "off the bat". It has been reported to me that currently the LiveCD requires some tweaking at startup to adjust it to a given locale, which I feel is to ask too much precisely from users that are not skilled. Goal: a LiveCD version that is localized in Spanish from startup, with no tweaking required, to be distributable among the Spanish-speaking public.
*::Contact: yamaplos at bolinux.org

=== on Sugar hardware ports===
:First, see the '''[[Supported systems]]''' page.

* 

=== on Sugar activities===
:First, see the [[Activity Team]] pages.

* 

=== on Sugar deployments===
:First, see the [[Deployment Team]] pages.

* 

=== on Sugar Labs===
: See the '''[[Sugar Labs]]''' page. Sugar Labs was created to provide a mechanism for supporting the Sugar community of volunteers. These volunteers are engaged in a variety of activities: some are writing software to improve Sugar; some are porting Sugar to new platforms; some are developing new activities that run in Sugar; some are helping to debug Sugar and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios for learning with Sugar; some are using Sugar and reporting upon their experiences to the community; and some are providing help and support.

:Since we started Sugar Labs, we have been receiving a number of requests for help: porting Sugar to new distributions; tuning Sugar on a specific hardware platform; developing specific Sugar activity; helping with support in specific deployments, etc. Please use this page both to make requests and respond to requests for help.

* 

[[Category:General public]]
[[Category:Help]]

Supported systems

2010-03-10T17:33:08Z

David Kergyl: /* Starch */ Update links for XO-LiveCD

<noinclude>{{GoogleTrans-en}}</noinclude>
{{TOCright}}
:<big>'''Note:''' Development changes occur rapidly, and the documentation here lags the current state of systems development. For the latest information on any development project, visit their work sites.</big>

See [[Sugar Application Stack]] for a picture of the software stack.
=== Ways to run Sugar ===

Determine which of the various methods of running Sugar meet your needs:
* '''Pre-installed Sugar:'''
*: Some computers come with Sugar pre-installed, most notably the OLPC XO-1 laptop.
* '''LiveCD/LiveUSB:'''
*: Suitable for trying Sugar without having to install any software on almost any computer—just boot Sugar off of a CD or USB drive. For USB Solutions goto our [[Sugar on a Stick]] project page.
* '''Install Sugar:'''
*: If you are running one of the currently supported distributions, you can install Sugar using your systems standard package manager, e.g., Synaptic, apt-get, or yum.
* '''Emulator/Virtualizer:'''
*: [[QEMU]], [[VirtualBox]], or [[VMware]] let you run Sugar in an emulator or by virtualization on your computer—you'll need to install an emulator from which you launch Sugar and one of the [[Emulator image files]].
Refer to the [[#Table of Sugar solutions|matrix]] below to find a Sugar solution that works for you.

=== Computer labs ===

* Bill Kerr has written up instructions for trying Sugar in computer labs which run only Windows
*:(Please see [http://billkerr2.blogspot.com/2008/07/evaluating-sugar-in-developed-world.html].)

* Caroline Meeks is developing a deployment model that only requires one USB stick per child. (Please see [[Sugar on a Stick]].)

==Matrix of Sugar solutions==
There are many ways to run Sugar:
* As a [[#Starch|complete disk image]] on an existing machine;
* As a [[#Sucrose|session]] on a Linux system; or
* As part of a [[#Systems|complete hardware-software platform]].

===[[/Technical considerations | Technical considerations]]===
: A discussion of '''technical considerations''' regarding supported systems.

===Starch===

[[Image:Sugar-on-CD-USB.jpg]]

[[Taxonomy#Starch.28es.29:_A_complete_disk_image_for_Sugar|Starch]] is a complete disk image for Sugar.

{|border=1
|+ '''A complete disk image for Sugar'''
|-
!Name
!Sugar Version
!Tested
!Notes
|-
|[[Sugar on a Stick]]
|0.84
|In process
|This is a Live USB of the Sugar, and one of the primary focuses of Sugar development.
|-
|[ftp://rohrmoser-engineering.de/pub/XO-LiveCD/XO-LiveCD_091203.iso LiveBackup XO-LiveCD]
|0.82
|No
|This is a Live CD of the OLPC system. [ftp://rohrmoser-engineering.de/pub/XO-LiveCD/XO-LiveCD_090308.pdf Release Notes]
|-
|[[Image:Fedora.jpg|30px]]
|0.84.2
|yes
|Sugar Desktop on a Stick is a Fedora11 Sugar USB.img [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Linux#Download_of_Prebuilt_SUGAR-DESKTOP_USB.img_file] "real install" 4GB stick
|-
|[[Image:Fedora.jpg|30px]]
|
|
|Sugar on a Stick is a Fedora Live USB. There is also [http://dev.laptop.org/~cjb/rawhide-xo/ Fedora "Rawhide" on XO] development.
|-
|[[Image:Ubuntu.jpg|30px]][http://dev.laptop.org/~probono/sbuntu/ Ubuntu LiveCD/LiveUSB]
|0.82
|
|Instructions for installing a Ubuntu LiveUSB
|}

===Sucrose===

[[Taxonomy#Sucrose:_The_interface.2C_plus_a_set_of_demonstration_activities|Sucrose]] is the Sugar interface plus a set of demonstration activities. System maintainers should visit the [[Packaging Team]] page.

{|border=1
|+ '''The interface, plus a set of demonstration activities'''
|-
!Operating System !! Version !! Sugar Version !! Bundled !! Tested !! [[Packaging Team|Collaboration Links]] !! Notes
|-
|colspan=7 align=center|binary packages available
|-
|[[Image:Debian.jpg|30px]]Debian||4.0||0.82||Yes||Yes|| || [[Community/Distributions/Debian | Sugar on Debian]]
|-
|[[Image:Fedora.jpg|30px]]Fedora||7,8,9||0.82||Yes||Yes|| || [[Community/Distributions/Fedora | Sugar on Fedora]]
|-
|[[Image:Ubuntu.jpg|30px]]Ubuntu||8.04 (Hardy)||0.79.0-0ubuntu3||Yes||Yes||http://wiki.ubuntu.com/SugarTeam|| [[Community/Distributions/Ubuntu | Sugar on Ubuntu]]
|-
| ||8.10 (Intrepid)||0.82||Yes|| || || [[Community/Distributions/Ubuntu#Sucrose_0.82 | Sugar on Ubuntu]]
|-
| ||9.04 (Jackalope) 9.10 (Koala)||0.84||Yes|| || || [[Community/Distributions/Ubuntu#Sugar on Ubuntu 9.04 (jaunty) | Sugar on Jackalope or Koala]]
|-
|[[Image:Alt_linux_team_small.png|36px]]ALT Linux||4.1 Sisyphus||0.82 SugarPlatform-0.84||Yes|||| || [[Community/Distributions/ALTLinux | Sugar on ALT Linux]]
|-
|[[Image:mandriva.png|36px]]Mandriva||2009.1 Cooker||SugarPlatform-0.84 SugarPlatform-0.84||Yes Yes|||| ||[[Community/Distributions/Mandriva | Sugar on Mandriva]]
|-
|[[Image:Caixa Mágica.png|36px]]Caixa Mágica||12||SugarPlatform-0.84||Yes|| || || [[Community/Distributions/Magalhães | Sugar on Magalhães]]
|-
|colspan=7 align=center|packages not pre-built
|-
|[[Image:Gentoo-logo.svg|36px]]Gentoo||2009-03-19||0.84 9999||Yes|| || || [[Community/Distributions/Gentoo | Sugar on Gentoo]]
|-
|[[Image:Suse-small.jpg|36px]]OpenSUSE||11.1||0.84||Yes|| ||http://en.opensuse.org/Sugar IRC Freenode #opensuse-edu|| [http://en.opensuse.org/Sugar Sugar on OpenSUSE]]
|-
|[[Image:Apple.gif|36px]]|| || || || || || [[Supported_systems/Mac|Sugar on a Mac (in emulation)]]
|-
|[[Image:Slackware.png|65px]]||Slackware 12|| || || || ||[http://wiki.laptop.org/go/Sugar_on_Slackware Sugar on Slackware]
|-
|[[Image:XP.gif|78px]]||WindowsXP|| || ||No|| || [[Supported systems/Windows|Sugar on Windows (using QEMU)]]
|}

===Sugar for various hardware systems===
Since Sugar is now available on most major GNU/Linux distributions, it is possible to run Sugar almost any computer that can run GNU/Linux. We highlight some systems below. Please add your favorite to the list.

{|border=1
|+ '''Complete Sugar Solutions'''
|-
!Manufacturer
!Model
!Operating System
!Tested
!Notes
|-
| [http://www.laptop.org OLPC]
| XO-1
| Fedora 9
| Yes
| Standard (reference) distribution
|-
| [http://www.asus.com ASUSTeK]
| Eee PC
|
| In initial testing phase
|
|-
| [http://www.intel.com Intel]
| Classmate Gen 1 & Gen 2
|
| under development
|
|}

== Getting the Sugar sources ==
Distributors can find the latest sources for the sucrose components [[Development Team/Release/CurrentRelease/Sucrose#Getting_the_sources|here]]. Each [http://sugarlabs.org/go/Development_Team/Release/Roadmap#Schedule sucrose roadmap] entry has as well links to the release pages of earlier releases.

==Updating Sugar to the Latest Version==


[http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu http://wiki.sugarlabs.org/images/e/e2/Ubuntu.jpg]


===Ubuntu===

The Sugar packages in
Ubuntu 9.04 and 8.10 [http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu#Using_sugar_PPAs.]

For a LiveCD/LiveUSB, check out the instructions [http://dev.laptop.org/~probono/sbuntu/].

Updated sucrose packages are usually published in a PPA: See [[Community/Distributions/Ubuntu#Sugar_on_Ubuntu_8.04|here]] for details.

If you want up-to-the-minute freshness (and brokenness) you can use [[Development Team/Jhbuild|jhbuild]] to build from source instead of the released packages. Follow the instructions [[Development Team/Jhbuild#Creating_an_xsession_for_Sugar-jhbuild|here]] to install sugar-jhbuild as an xsession option.


[http://wiki.sugarlabs.org/go/Community/Distributions/Debian http://wiki.sugarlabs.org/images/a/a1/Debian.jpg]


===Debian===

Sucrose packages are usually updated in unstable. These packages migrate to testing after a while. You can see the current package versions [http://packages.debian.org/search?keywords=sugar&searchon=names&suite=all&section=all here].

If you want up-to-the-minute freshness (and brokenness) you can use [[Development Team/Jhbuild|jhbuild]] to build from source instead of the released packages.


[http://wiki.sugarlabs.org/go/Community/Distributions/Fedora http://wiki.sugarlabs.org/images/1/1e/Fedora.jpg]


===Fedora===

==== Fedora LiveCD/Live USB ====
:Project page: https://fedoraproject.org/wiki/Sugar_Spin

With this spin, you'll be able to run Sugar, which is developed by Sugarlabs and the desktop environment used on the OLPC, directly from a Live CD! You'll find several activities on the image including most notably...

* sugar-browse - a web browsing activity based on xulrunner
* sugar-write - a word processor based on abiword

...along with several other activities including Chat support.

:See our [[Sugar_on_a_Stick | Sugar on a Stick page]].

The Fedora OLPC SIG, https://fedoraproject.org/wiki/OLPC, will be importing further activities into Fedora, which might be installed using ''yum install sugar-*'' at a later time.

:Recent development spins:
::http://download.sugarlabs.org/soas/snapshots/1/

For more information, please refer to the announcement here:

https://www.redhat.com/archives/fedora-olpc-list/2008-December/msg00061.html

Fedora 11 Preview contains USB Creator which can make USB and SD's with persistence of Fedora F11 (and Sugar if added with Synaptic) and Soas-beta's [satellit 04/30/2009]

What if you wanted to put it quickly onto your USB Key? You'll just need to grab Luke Macken's liveusb-creator, which already includes support for the Sugar Spin. Here's the link:

:http://fedorahosted.org/liveusb-creator/

The liveusb-creator still contains an old link, which is the reason why you'll need to download the spin manually until this gets fixed.

'''Tip of the hat:''' Sebastian Dziallas and the Fedora team

==== Fedora on an OLPC XO ====

On an OLPC XO-1 laptop, run olpc-update as root.

Normally you only need to run ''olpc-update'' in the Terminal application with a build number, like this:

# sudo olpc-update 767

'''Note:''' Now you can do this by means of the graphical [[olpc:Sugar Control Panel|Sugar Control Panel]].

===OLPC Clean Install===

http://wiki.laptop.org/go/Clean-install_procedure

====Joyride====
See [[OLPC:Future releases]], the Joyride train is in the round house.

<big>Joyride is for developers; it is not supported. Joyride builds may cause data corruption and in rare cases, even cause hardware damage, so please do not use Joyride on mission-critical systems.</big>

Joyride contains all the "bleeding-edge" features that are being debugged for inclusion in the next release.

Open the Terminal application and type the following, substituting 2469 for the latest version number.

# olpc-update joyride-2469

'''What's the latest version?''' You can find the latest build number (shown above as 1779) at the bottom of http://xs-dev.laptop.org/~cscott/xo-1/streams/joyride/

Updates usually takes 10–15 minutes. It's advised that you plug your XO in while Sugar updates itself, then reboot it to see the new OS take effect.

==== Other Options ====

These are options that can be used with the update command:

# olpc-update --help
<pre><nowiki>
Usage:
olpc-update [options] --hints hints-file
olpc-update [options] [-rf] build-number
olpc-update [options] [-rf] --usb
olpc-update --version
olpc-update --help

For example:
olpc-update 630
olpc-update joyride-1779
olpc-update update.1-700

Options:
-h, --help show this help message and exit
-f, --full skip incremental update attempt.
--force force update to an unsigned build.
-r, --reboot reboot after a successful update.
--hints=FILE name of json-encoded hints dictionary identifying the desired
new version.
-u, --usb upgrade from new build on inserted USB stick.
-v display verbose progress information; repeat for more verbose
output.
-q, --quiet don't output anything; use exit status to indicate success.
--version display version and license information.
</nowiki></pre>


[http://wiki.sugarlabs.org/go/Community/Distributions/Gentoo http://wiki.sugarlabs.org/images/5/5e/Gentoo-logo-small.jpg]


==== Fedora on the XO-1 ====

One of the updated ways of installing sugar on the XO can be seen here.

http://wiki.laptop.org/go/F11_for_XO-1

==== SOAS on the XO ====
You can also install sugar on a stick on the XO-1

* [[Sugar_on_a_Stick/Installation/OLPC]]

===Gentoo===
* There are two methods to get Sugar on your Gentoo box: [[Community/Distributions/Gentoo#sugar-jhbuild|sugar-jhbuild]] and [[Community/Distributions/Gentoo#Sugar overlay|Sugar overlay]]. '''See''' [[Community/Distributions/Gentoo|Gentoo]] for details.


[http://wiki.sugarlabs.org/go/Community/Distributions/ALTLinux http://wiki.sugarlabs.org/images/5/55/Alt_linux_team_tiny.png]


===ALT Linux===
* ALT Linux Team is an international software developers team, collectively working on [http://en.altlinux.org/Sisyphus Sisyphus].

*'''To install''' Sugar try these [[Community/Distributions/ALTLinux#Setup|packages]].


[http://wiki.sugarlabs.org/go/Community/Distributions/Mandriva http://wiki.sugarlabs.org/images/2/2b/Mandriva.png]


===Mandriva===
To install Sugar on Mandriva follow these [[Community/Distributions/Mandriva#Setup|instructions]].

Supported systems

2010-03-10T17:18:15Z

David Kergyl: /* Starch */ Mark broken links.

<noinclude>{{GoogleTrans-en}}</noinclude>
{{TOCright}}
:<big>'''Note:''' Development changes occur rapidly, and the documentation here lags the current state of systems development. For the latest information on any development project, visit their work sites.</big>

See [[Sugar Application Stack]] for a picture of the software stack.
=== Ways to run Sugar ===

Determine which of the various methods of running Sugar meet your needs:
* '''Pre-installed Sugar:'''
*: Some computers come with Sugar pre-installed, most notably the OLPC XO-1 laptop.
* '''LiveCD/LiveUSB:'''
*: Suitable for trying Sugar without having to install any software on almost any computer—just boot Sugar off of a CD or USB drive. For USB Solutions goto our [[Sugar on a Stick]] project page.
* '''Install Sugar:'''
*: If you are running one of the currently supported distributions, you can install Sugar using your systems standard package manager, e.g., Synaptic, apt-get, or yum.
* '''Emulator/Virtualizer:'''
*: [[QEMU]], [[VirtualBox]], or [[VMware]] let you run Sugar in an emulator or by virtualization on your computer—you'll need to install an emulator from which you launch Sugar and one of the [[Emulator image files]].
Refer to the [[#Table of Sugar solutions|matrix]] below to find a Sugar solution that works for you.

=== Computer labs ===

* Bill Kerr has written up instructions for trying Sugar in computer labs which run only Windows
*:(Please see [http://billkerr2.blogspot.com/2008/07/evaluating-sugar-in-developed-world.html].)

* Caroline Meeks is developing a deployment model that only requires one USB stick per child. (Please see [[Sugar on a Stick]].)

==Matrix of Sugar solutions==
There are many ways to run Sugar:
* As a [[#Starch|complete disk image]] on an existing machine;
* As a [[#Sucrose|session]] on a Linux system; or
* As part of a [[#Systems|complete hardware-software platform]].

===[[/Technical considerations | Technical considerations]]===
: A discussion of '''technical considerations''' regarding supported systems.

===Starch===

[[Image:Sugar-on-CD-USB.jpg]]

[[Taxonomy#Starch.28es.29:_A_complete_disk_image_for_Sugar|Starch]] is a complete disk image for Sugar.

{|border=1
|+ '''A complete disk image for Sugar'''
|-
!Name
!Sugar Version
!Tested
!Notes
|-
|[[Sugar on a Stick]]
|0.84
|In process
|This is a Live USB of the Sugar, and one of the primary focuses of Sugar development.
|-
|[ftp://rohrmoser-engineering.de/pub/XO-LiveCD/XO-LiveCD_090110.iso LiveBackup XO-LiveCD] (Link broken 3/10/10)
|0.82
|No
|This is a Live CD of the OLPC system. [ftp://rohrmoser-engineering.de/pub/XO-LiveCD/XO-LiveCD_090110.pdf Release Notes] (This link is broken as of March 10, 2010.)
|-
|[[Image:Fedora.jpg|30px]]
|0.84.2
|yes
|Sugar Desktop on a Stick is a Fedora11 Sugar USB.img [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Linux#Download_of_Prebuilt_SUGAR-DESKTOP_USB.img_file] "real install" 4GB stick
|-
|[[Image:Fedora.jpg|30px]]
|
|
|Sugar on a Stick is a Fedora Live USB. There is also [http://dev.laptop.org/~cjb/rawhide-xo/ Fedora "Rawhide" on XO] development.
|-
|[[Image:Ubuntu.jpg|30px]][http://dev.laptop.org/~probono/sbuntu/ Ubuntu LiveCD/LiveUSB]
|0.82
|
|Instructions for installing a Ubuntu LiveUSB
|}

===Sucrose===

[[Taxonomy#Sucrose:_The_interface.2C_plus_a_set_of_demonstration_activities|Sucrose]] is the Sugar interface plus a set of demonstration activities. System maintainers should visit the [[Packaging Team]] page.

{|border=1
|+ '''The interface, plus a set of demonstration activities'''
|-
!Operating System !! Version !! Sugar Version !! Bundled !! Tested !! [[Packaging Team|Collaboration Links]] !! Notes
|-
|colspan=7 align=center|binary packages available
|-
|[[Image:Debian.jpg|30px]]Debian||4.0||0.82||Yes||Yes|| || [[Community/Distributions/Debian | Sugar on Debian]]
|-
|[[Image:Fedora.jpg|30px]]Fedora||7,8,9||0.82||Yes||Yes|| || [[Community/Distributions/Fedora | Sugar on Fedora]]
|-
|[[Image:Ubuntu.jpg|30px]]Ubuntu||8.04 (Hardy)||0.79.0-0ubuntu3||Yes||Yes||http://wiki.ubuntu.com/SugarTeam|| [[Community/Distributions/Ubuntu | Sugar on Ubuntu]]
|-
| ||8.10 (Intrepid)||0.82||Yes|| || || [[Community/Distributions/Ubuntu#Sucrose_0.82 | Sugar on Ubuntu]]
|-
| ||9.04 (Jackalope) 9.10 (Koala)||0.84||Yes|| || || [[Community/Distributions/Ubuntu#Sugar on Ubuntu 9.04 (jaunty) | Sugar on Jackalope or Koala]]
|-
|[[Image:Alt_linux_team_small.png|36px]]ALT Linux||4.1 Sisyphus||0.82 SugarPlatform-0.84||Yes|||| || [[Community/Distributions/ALTLinux | Sugar on ALT Linux]]
|-
|[[Image:mandriva.png|36px]]Mandriva||2009.1 Cooker||SugarPlatform-0.84 SugarPlatform-0.84||Yes Yes|||| ||[[Community/Distributions/Mandriva | Sugar on Mandriva]]
|-
|[[Image:Caixa Mágica.png|36px]]Caixa Mágica||12||SugarPlatform-0.84||Yes|| || || [[Community/Distributions/Magalhães | Sugar on Magalhães]]
|-
|colspan=7 align=center|packages not pre-built
|-
|[[Image:Gentoo-logo.svg|36px]]Gentoo||2009-03-19||0.84 9999||Yes|| || || [[Community/Distributions/Gentoo | Sugar on Gentoo]]
|-
|[[Image:Suse-small.jpg|36px]]OpenSUSE||11.1||0.84||Yes|| ||http://en.opensuse.org/Sugar IRC Freenode #opensuse-edu|| [http://en.opensuse.org/Sugar Sugar on OpenSUSE]]
|-
|[[Image:Apple.gif|36px]]|| || || || || || [[Supported_systems/Mac|Sugar on a Mac (in emulation)]]
|-
|[[Image:Slackware.png|65px]]||Slackware 12|| || || || ||[http://wiki.laptop.org/go/Sugar_on_Slackware Sugar on Slackware]
|-
|[[Image:XP.gif|78px]]||WindowsXP|| || ||No|| || [[Supported systems/Windows|Sugar on Windows (using QEMU)]]
|}

===Sugar for various hardware systems===
Since Sugar is now available on most major GNU/Linux distributions, it is possible to run Sugar almost any computer that can run GNU/Linux. We highlight some systems below. Please add your favorite to the list.

{|border=1
|+ '''Complete Sugar Solutions'''
|-
!Manufacturer
!Model
!Operating System
!Tested
!Notes
|-
| [http://www.laptop.org OLPC]
| XO-1
| Fedora 9
| Yes
| Standard (reference) distribution
|-
| [http://www.asus.com ASUSTeK]
| Eee PC
|
| In initial testing phase
|
|-
| [http://www.intel.com Intel]
| Classmate Gen 1 & Gen 2
|
| under development
|
|}

== Getting the Sugar sources ==
Distributors can find the latest sources for the sucrose components [[Development Team/Release/CurrentRelease/Sucrose#Getting_the_sources|here]]. Each [http://sugarlabs.org/go/Development_Team/Release/Roadmap#Schedule sucrose roadmap] entry has as well links to the release pages of earlier releases.

==Updating Sugar to the Latest Version==


[http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu http://wiki.sugarlabs.org/images/e/e2/Ubuntu.jpg]


===Ubuntu===

The Sugar packages in
Ubuntu 9.04 and 8.10 [http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu#Using_sugar_PPAs.]

For a LiveCD/LiveUSB, check out the instructions [http://dev.laptop.org/~probono/sbuntu/].

Updated sucrose packages are usually published in a PPA: See [[Community/Distributions/Ubuntu#Sugar_on_Ubuntu_8.04|here]] for details.

If you want up-to-the-minute freshness (and brokenness) you can use [[Development Team/Jhbuild|jhbuild]] to build from source instead of the released packages. Follow the instructions [[Development Team/Jhbuild#Creating_an_xsession_for_Sugar-jhbuild|here]] to install sugar-jhbuild as an xsession option.


[http://wiki.sugarlabs.org/go/Community/Distributions/Debian http://wiki.sugarlabs.org/images/a/a1/Debian.jpg]


===Debian===

Sucrose packages are usually updated in unstable. These packages migrate to testing after a while. You can see the current package versions [http://packages.debian.org/search?keywords=sugar&searchon=names&suite=all&section=all here].

If you want up-to-the-minute freshness (and brokenness) you can use [[Development Team/Jhbuild|jhbuild]] to build from source instead of the released packages.


[http://wiki.sugarlabs.org/go/Community/Distributions/Fedora http://wiki.sugarlabs.org/images/1/1e/Fedora.jpg]


===Fedora===

==== Fedora LiveCD/Live USB ====
:Project page: https://fedoraproject.org/wiki/Sugar_Spin

With this spin, you'll be able to run Sugar, which is developed by Sugarlabs and the desktop environment used on the OLPC, directly from a Live CD! You'll find several activities on the image including most notably...

* sugar-browse - a web browsing activity based on xulrunner
* sugar-write - a word processor based on abiword

...along with several other activities including Chat support.

:See our [[Sugar_on_a_Stick | Sugar on a Stick page]].

The Fedora OLPC SIG, https://fedoraproject.org/wiki/OLPC, will be importing further activities into Fedora, which might be installed using ''yum install sugar-*'' at a later time.

:Recent development spins:
::http://download.sugarlabs.org/soas/snapshots/1/

For more information, please refer to the announcement here:

https://www.redhat.com/archives/fedora-olpc-list/2008-December/msg00061.html

Fedora 11 Preview contains USB Creator which can make USB and SD's with persistence of Fedora F11 (and Sugar if added with Synaptic) and Soas-beta's [satellit 04/30/2009]

What if you wanted to put it quickly onto your USB Key? You'll just need to grab Luke Macken's liveusb-creator, which already includes support for the Sugar Spin. Here's the link:

:http://fedorahosted.org/liveusb-creator/

The liveusb-creator still contains an old link, which is the reason why you'll need to download the spin manually until this gets fixed.

'''Tip of the hat:''' Sebastian Dziallas and the Fedora team

==== Fedora on an OLPC XO ====

On an OLPC XO-1 laptop, run olpc-update as root.

Normally you only need to run ''olpc-update'' in the Terminal application with a build number, like this:

# sudo olpc-update 767

'''Note:''' Now you can do this by means of the graphical [[olpc:Sugar Control Panel|Sugar Control Panel]].

===OLPC Clean Install===

http://wiki.laptop.org/go/Clean-install_procedure

====Joyride====
See [[OLPC:Future releases]], the Joyride train is in the round house.

<big>Joyride is for developers; it is not supported. Joyride builds may cause data corruption and in rare cases, even cause hardware damage, so please do not use Joyride on mission-critical systems.</big>

Joyride contains all the "bleeding-edge" features that are being debugged for inclusion in the next release.

Open the Terminal application and type the following, substituting 2469 for the latest version number.

# olpc-update joyride-2469

'''What's the latest version?''' You can find the latest build number (shown above as 1779) at the bottom of http://xs-dev.laptop.org/~cscott/xo-1/streams/joyride/

Updates usually takes 10–15 minutes. It's advised that you plug your XO in while Sugar updates itself, then reboot it to see the new OS take effect.

==== Other Options ====

These are options that can be used with the update command:

# olpc-update --help
<pre><nowiki>
Usage:
olpc-update [options] --hints hints-file
olpc-update [options] [-rf] build-number
olpc-update [options] [-rf] --usb
olpc-update --version
olpc-update --help

For example:
olpc-update 630
olpc-update joyride-1779
olpc-update update.1-700

Options:
-h, --help show this help message and exit
-f, --full skip incremental update attempt.
--force force update to an unsigned build.
-r, --reboot reboot after a successful update.
--hints=FILE name of json-encoded hints dictionary identifying the desired
new version.
-u, --usb upgrade from new build on inserted USB stick.
-v display verbose progress information; repeat for more verbose
output.
-q, --quiet don't output anything; use exit status to indicate success.
--version display version and license information.
</nowiki></pre>


[http://wiki.sugarlabs.org/go/Community/Distributions/Gentoo http://wiki.sugarlabs.org/images/5/5e/Gentoo-logo-small.jpg]


==== Fedora on the XO-1 ====

One of the updated ways of installing sugar on the XO can be seen here.

http://wiki.laptop.org/go/F11_for_XO-1

==== SOAS on the XO ====
You can also install sugar on a stick on the XO-1

* [[Sugar_on_a_Stick/Installation/OLPC]]

===Gentoo===
* There are two methods to get Sugar on your Gentoo box: [[Community/Distributions/Gentoo#sugar-jhbuild|sugar-jhbuild]] and [[Community/Distributions/Gentoo#Sugar overlay|Sugar overlay]]. '''See''' [[Community/Distributions/Gentoo|Gentoo]] for details.


[http://wiki.sugarlabs.org/go/Community/Distributions/ALTLinux http://wiki.sugarlabs.org/images/5/55/Alt_linux_team_tiny.png]


===ALT Linux===
* ALT Linux Team is an international software developers team, collectively working on [http://en.altlinux.org/Sisyphus Sisyphus].

*'''To install''' Sugar try these [[Community/Distributions/ALTLinux#Setup|packages]].


[http://wiki.sugarlabs.org/go/Community/Distributions/Mandriva http://wiki.sugarlabs.org/images/2/2b/Mandriva.png]


===Mandriva===
To install Sugar on Mandriva follow these [[Community/Distributions/Mandriva#Setup|instructions]].