View source for Sugar Creation Kit/sck/Advanced Topics



== Sweets Distribution==
===[[Sugar_Network/Tutorial|Sugar Network Tutorial]]===
*Annotated screen shots with Links
===[[Platform_Team/Sweets/Getting_started| Sweets-Getting Started]]===
:Click on title ^ to go to topic
*Some ideas on how to present SWEETS. (Inkyfingers)
*look at [[Platform_Team/Infrastructure| Infrastructure]] for an overview.
===[[Sweets Distribution]]===
:Click on title ^ to go to topic
:(Sweets Distribution is easier to use for Ubuntu' and its Derivatives (Adding an additional Repository to apt) as the packages are pre-configured, ready to use.)
:*[[Sweets Distribution]]
::(Developed for [[Trisquel_On_A_Sugar_Toast|Trisquel-sugar-Toast]] )

===[[Platform_Team/Sweets|Sweets]]===
:Click on title ^ to go to topic
:(Advanced)
:Debian, Ubuntu, Fedora, Mandriva, openSUSE, and Gentoo
*[[Platform_Team/Guide/Sweets_Usage|Sweets Usage]]
*[[Platform_Team/Guide/Sugar_via_Sweets|Sugar via Sweets]]
:(This guide describes how to run Sugar using Sugar Packaging Management System, Sweets.)
:[[Platform_Team/Sweets/Getting_started|Request for better Documentation of installs]]
::[[Talk:Platform_Team/Guide/Sugar_via_Sweets#Installing_sweets-sugar_from_Fedora_16_GNOME_3_Terminal|Log of Installation of sugar-sweets 0.88 and 0.94 on f16-GNOME3-shell]]
::[[Talk:Platform_Team/Guide/Sugar_via_Sweets#Installing_Sugar_via_sweets_-_in_Mint-12|Installing_Sugar_via_sweets_-_in_Mint-12]]
::[[Talk:Platform_Team/Guide/Sugar_via_Sweets#Installing_Sugar_via_sweets_-_in_Debian_testing_Wheezy|Installing_Sugar_via_sweets_-_in_Debian_testing_Wheezy]]
*[[Platform_Team/Guide/Sweets_Packaging|sweets packaging]]
:(For developers)

==[[Platform_Team/Sugar_Network|Sugar Network]]==
:Click on title ^ to go to topic
*Overview: [[Sugar_Network/Concept]]
:Collaboration support for Internet-less environments (but not only)
*[[Sugar Network Activities| Sugar Network Activities when f8 key is pressed]]
:Tests of which activities start by page

===[[Harmonic Distribution]]===
*Look at this tutorial: [[Sugar_Network/Tutorial]]
 * The possibility to launch Base Software in heterogeneous
   software and hardware environments.
 * Using Base Software, provide access to various Content
   (Sugar activities, artifacts created by Sugar activities, books, etc.)
   created within the Sugar community.
 * Using Base Software, provide collaborative functionality to
   support Social activity around the Content.
 * Instruments and workflows to adapt Content and Base Software
   to specific needs that Sugar Deployment might face,
   including extreme ones like off-line environments and restricting
   hardware.

*[Sugar-devel] [SWEETS] Testing collaboration related fixes 05/07/2012
 Hi all!
 Following the plan for Harmonic Distribution v0.2 (which will be a basis
 for Sugar Distribution to use in peruvian pilot), in Sugar Shell code
 were made fixes that are intended to make Telepathy (everything related to
 Neighbourhood view and Sugar Activities sharing/joining) more stable
 (that was broken since global redesign started after 0.88 release).
 Fixes are accessible from SweetsDistribution:Factory repository. Follow
 regular Sweets Distribution installation instructions[1] to install
 fixed Sugar Shell on all supported platforms[2].
 Some visible changes in F1 view:
 * the number of buddies should be increased from ~20 to 70-90
   some Sugar versions (maybe 0.90-0.92) don't publish information about
   nickname/colors on regular basis; this information are being stored on
   disk for now
 * for some buddies, server still don't have information about colors
   (replaced by gray) and nick names (jabber ids)
 If you have a time and want to help Puno deployment pilot, please,
 consider possibility to install sweets-desktop from Factory repository
 and do some testing of collaboration functionality.
 
 Some tips:
 
 * while interacting with another buddies, make sure that all
   participants use Sweets Distribution (some F1 buddies might misbehave)
 * the good criteria of stability level of new Sugar is comparing with
   how collaboration happen in 0.88 Sugar.
 Source code, for interested in people, can be found in top commits from:
 
 * http://git.sugarlabs.org/desktop/sugar
 * http://git.sugarlabs.org/desktop/sugar-toolkit
 * http://git.sugarlabs.org/server/prosody-sugar
 [1] [[Sweets_Distribution#Installation]]
 [2] [[Sweets_Distribution/Supported_platforms]]
 
 -- Aleksey
 Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

==[http://fedoraproject.org/wiki/Features/BoxGrinder BoxGrinder]==
:BoxGrinder Build is an easy to use command line tool to create appliances (virtual images) from simple plaintext appliance definition files. BoxGrinder can produce appliances for a variety of virtual and cloud platforms using plugins supporting technologies such as VMware or EC2. 
*http://boxgrinder.org
*http://boxgrinder.org/community/
*http://boxgrinder.org/tutorials/
*http://boxgrinder.org/tutorials/boxgrinder-build-meta-appliance/
*http://boxgrinder.org/download/boxgrinder-build-meta-appliance/

==[https://fedorahosted.org/pungi/wiki/PungiDocs/RunningPungi Pungi]==
::'''Advanced '''
*used to build non-live CD/DVD isos
 Pungi needs to run on the arch it is composing, as root, and with an install of what it is composing, eg if you are composing Fedora 8, you need to be running Fedora 8.
 This is so that the correct userland tools are used to create the images and such used by anaconda.
 The eventual usage of pungi will most likely be in mock chroots to facilitate this.
 It needs to run on the arch it is composing due to how anaconda-runtime determines what files to put in the boot images at this time.
 Currently the releases of pungi are designed to run on an updated Rawhide system. Development of pungi always tracks Rawhide.
;The following  sections..." assume you have installed the [https://admin.fedoraproject.org/pkgdb/acls/name/mock mock package] and prepared the mock chroot"
====[https://fedoraproject.org/wiki/How_to_create_a_Fedora_install_ISO_for_testing?rd=How_to_build_a_Rawhide_ISO_image_for_testing#Build_a_boot.iso Build a boot.iso]====
*"This section provides instruction on creating PXEboot and boot.iso images"

====[https://fedoraproject.org/wiki/How_to_create_a_Fedora_install_ISO_for_testing?rd=How_to_build_a_Rawhide_ISO_image_for_testing Build a DVD.iso]====
*"This section assumes you have installed the [https://admin.fedoraproject.org/pkgdb/acls/name/mock mock package] and prepared the mock chroot"

==[http://fedoraproject.org/wiki/Koji Koji]==
:Click on title ^ to go to topic
;:(Very Advanced)

:Koji is the software that builds RPM packages for the Fedora project

==[https://fedoraproject.org/wiki/How_to_create_an_RPM_package How to create an RPM package]==
*How to create an RPM package in Fedora 
:https://fedoraproject.org/wiki/How_to_create_an_RPM_package

==sugar-build==
;http://sugarlabs.org/~dnarvaez/sugar-docs/build.html
*better j-build

==Git==
:Advanced - Used by Sugar Developers
*[[Activity_Team/Git_Migration |How to migrate activity source control from laptop.org to sugarlabs.org]]
*[[Activity_Team/Git_Tutorial|Getting started with Gitorious, a web based Git service provided by Sugar Labs]]
*Nice introduction to git: http://try.github.com/levels/1/challenges/1
===Tutorials===
*[[Activity_Team/Activity_Development_Fedora_17| Activity Development in Fedora 17 using Git]]
*[http://www.archive.org/details/MakeYourOwnSugarActivities Make your own Sugar Activities]

===L10n Translations===
 There is a git user named "pootle" that acts as the proxy by which all
 PO file translations are committed from the Pootle server.  Please
 make pootle a committer on the repo and I will make the connections
 between git and the Pootle server.
 Some "best practices" about working with git and Pootle are described here.
 [[Translation_Team/i18n_Best_Practices#Do_not_touch_anything_inside_your_po_directory| Translation Team Best Practices]]

==[http://0pointer.de/blog/projects/resources systemd for Administrators]==
 "Resource Management in one way or another has been available in systemd for a while already,
 so it's really time we introduce this to the broader audience."
==[https://live.gnome.org/Vala/Tutorial Vala]==
 "Vala is a new programming language that allows modern programming techniques
 to be used to write applications that run on the GNOME runtime libraries,
 particularly GLib and GObject."

==[http://bemasc.net/~bens/groupthink/ groupthink]==
:Click on title ^ to go to topic
*Very Advanced
:"Groupthink is a library of self-sharing data structures written in python and shared over dbus.
:Together with the D-Bus Tubes provided by the Telepathy framework, this enables data structures to be shared over a network."

==[[OLPC | OLPC XO-1 and XO-1.5 links and Notes ]]==
:Click on title ^ to go to topic
===wiki.laptop.org===
:http://wiki.laptop.org/go/The_OLPC_Wiki
===Build 13.1.0===
:http://wiki.laptop.org/go/13.1.0
:http://build.laptop.org/13.1.0/os15/xo-1.5/

*PM on IRC dec 1 2012
 <satellit_e> still a problen here: if I change color in cp I loose jabber
 <satellit_e> same bug as in my remixes
 <satellit_e> should be same if change name also
 <satellit_e> only works with initial login name and colors
 <pbrobinson> That's an upstream bug
 <pbrobinson> You have an XO?
 <pbrobinson> if so what model?
 <satellit_e> I have X0-1 and 1.5  have requested 1.75 and tablet but no yet any response. submitter request thru olpc
 <satellit_e> adam also said he would get me some when he stay with us here in Bend Oregon..
 <pbrobinson> there will be a 13.1.0 os16 release at some point over the weekend, can you test the colour change on the 1.5 or 1.0 and see if the issue happens there
*http://bugs.sugarlabs.org/ticket/4289

==[http://sugardextrose.org/projects/dextrose/wiki/Testing_Dextrose_in_a_virtual_machine Testing Dextrose in a virtual machine]==
*Download Image; KVM; VirtualBox

==[[Dextrose/Building|Dextrose Building]]==
 Dextrose uses [http://wiki.laptop.org/go/OS_Builder olpc-os-builder], a tool create by OLPC to build official and customized system images.
 The Dextrose git repository contains, olpc-os-builder, local customizations specific to Dextrose,
 and fixes and enhancements waiting to be pushed upstream. 
*[[Dextrose/Building]]

==[http://wiki.laptop.org/go/XS_Installing_Software_0.7 XS Schoolserver 0.7]==
:Click on title ^ to go to topic
*How to install:http://wiki.laptop.org/go/XS_Installing_Software_0.7
*Download: http://dev.laptop.org/xs/OLPC-School-Server-0.7beta2-i386.iso
*http://schoolserver.wordpress.com/xs-installation/community-edition-xs-on-xo-1-75/
*Work in Progress: http://schoolserver.wordpress.com/xs-installation/xsce-on-xo-1-5/
===Manuals===
:[http://laptop.org/8.2.0/manual/ OLPC Manual]
:[http://wiki.laptop.org/go/OLPC_SanFranciscoBayArea/OLPCSF_Community_Summit_2011/Help_Activity_Refresh Help Activity Refresh]
:[http://wiki.laptop.org/go/Manuals Manuals Info]

==Kernel Userspace Interfaces==
*Reference for Linux kernel 2.6.23: http://people.ee.ethz.ch/~arkeller/linux/kernel_user_space_howto.html
==ARM==
*Proposed Fedora ARM Download Page: https://stg.fedoraproject.org/en/get-fedora-options#other --[[User:Satellit|Satellit]] 10:42, 18 December 2012 (EST)
=====References=====
:http://elinux.org/RPi_Distributions
:http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores
:http://www.linaro.org/downloads/
:RPM Fusion: http://rpmfusion.org/Architectures/ARM
:http://fedoraproject.org/wiki/Fedora_ARM_Installer
*https://fedoraproject.org/wiki/Architectures/ARM/AArch64/FoundationModel
*chromium-os Secure Boot Info: http://www.chromium.org/chromium-os/chromiumos-design-docs/verified-boot-crypto
*Tutorial: Android Development: https://fedoraproject.org/wiki/HOWTO_Setup_Android_Development

===[[Testing/Reports/ARM_TrimSlice|TrimSlice]]===
====Firmware Updater====
*http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater
====Ubuntu on a TrimSlice====
*Testing of TrimSlicePro
:[[Testing/Reports/ARM_TrimSlice#TrimSlicePro|TrimSlicePro-Update]]
*Testing of TrimSlice H250
:[[Testing/Reports/ARM_TrimSlice#TrimSlice_H250:_Install_Ubuntu_on_a_320_GB_HD|Install of Ubuntu to 320 GB HD]]
:[[Testing/Reports/ARM_TrimSlice#TrimSlice_H250:_Ubuntu_on_a_SDXC_Card| Install of Ubuntu to a SDXC Card]]

[[File:TS_SDXC.JPG|600px]]
*TrimSlicePro Setup Booted from 64 GB SDXC Card in front slot
:(SDXC card is expanded to 30 GB with gparted)
[[File:TS_with_Sugar.JPG|600px]]
*TrimSlicePro Running KDE-Desktop -plus sugar-emulator (0.90.1)
:Beautiful Display on Samsung SyncMaster S20B350 HDMI 1600x900 @60Hz PP

*https://wiki.ubuntu.com/ARM
*https://wiki.ubuntu.com/ARM/Server/Install
*https://wiki.ubuntu.com/ARM/RootfsFromScratch
*http://cdimage.ubuntu.com/daily-preinstalled/current/

====[https://fedoraproject.org/wiki/Architectures/ARM/Trimslice Fedora on a TrimSlice]====
*Installer:http://fedoraproject.org/wiki/Architectures/ARM/Installer

=====Fedora with XFCE=====
*  http://scotland.proximity.on.ca/arm-nightlies/
======References======
:http://scotland.proximity.on.ca/arm-nightlies/vault/f17arm-latest-arm-rpi-xfce-mmcblk0.img.xz
*http://scotland.proximity.on.ca/arm-nightlies/vault/f18arm-20120915-021653-armhfp-trimslice-mmcblk0.img.xz
:http://fedoraproject.org/wiki/Architectures/ARM
:http://fedoraproject.org/wiki/Architectures/ARM/Fedora_17_Beta
:https://fedoraproject.org/wiki/Architectures/ARM/Fedora17_rawhide
:http://dl.fedoraproject.org/pub/fedora-secondary/releases/test/17-Beta/Images/armhfp/
:f17-arm RC-1: http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC1/armhfp/
::Boot from CD: http://www.trimslice.com/forum/viewtopic.php?f=25&t=412
:linux-tegra-drm:https://gitorious.org/linux-tegra-drm/pages/Host1xIntroduction

======Tegra======
:http://developer.nvidia.com/tegra-2-technical-reference-manual
:http://www.trimslice.com/wiki/index.php/OS_Installation_and_update
:http://www.trimslice.com/wiki/index.php/Trim-Slice_Linux_Kernel
:http://lists.linux-foundation.org/pipermail/ksummit-2012-discuss/2012-June/000304.html
*Beta-Tegra Graphics drivers: https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-tegra/15~beta1-0ubuntu2
*Problem with permissions:http://forums.developer.nvidia.com/devforum/discussion/6296/console-broken-on-linux-tegra-nv-3-1
:https://gitorious.org/linux-tegra-drm
:::linux-tegra-drm:https://gitorious.org/linux-tegra-drm/pages/Host1xIntroduction

====f17-fedora-arm====
*Release  Jun 19, 2012 : http://fedoraproject.org/wiki/Architectures/ARM/Fedora_17_GA
*https://fedoraproject.org/wiki/Category:Fedora_ARM_Hardware
*http://fedoraproject.org/wiki/Architectures/ARM
*http://fedoraproject.org/wiki/Architectures/ARM/HowToQemu
=====f17 Nightly Images=====
*Nightly Composes: http://scotland.proximity.on.ca/arm-nightlies/
*Beta Release Criteria: http://fedoraproject.org/wiki/Architectures/ARM/Quality_Assurance/Beta_Release_Criteria
======live media creator on arm======
:http://fedoraproject.org/wiki/Anaconda/Features/ReworkLiveCD
:http://www.redhat.com/archives/anaconda-devel-list/2011-November/msg00081.html
:http://lists.fedoraproject.org/pipermail/arm/2012-May/003358.html

=====Trimslice Pro and H250=====
======Serial interface ONLY======
*Mac-Trimslice Pro Connections:
:Nice Terminal Emulator for Mac:http://www.macupdate.com/app/mac/31352/coolterm
*Connection Diagram:
 [MacBookPro USB port]---[usb to serial adapter (&)]---[null modem]--[serial cable]--(TrimSlice serial to mini cable]--[TrimSlice serial port]
:::::::::(&) DYNEX USB_PDA/Serial Adapter (Dynex DX-UD889)
*Console Speed 115200 bps, 8n1,
*root password: -Displays in serial terminal-
:'''root=fedoraarm'''

*Note these are experimental '''FOR TESTING ONLY''' - Still in development; use with caution
*The kernel used does not support startx 
:No graphical interfaces are available at this time for TrimSlicePro and TrimSlice -h
*dd will write a live USB but it will not boot in arm devices.
:works in intel PC's
*livecd-tools does not work

======SD Card Install======
*http://scotland.proximity.on.ca/arm-nightlies/vault/f17arm-latest-armhfp-trimslice-mmcblk0.img.xz
 This is a Fedora 17 Hard Float Trimslice Image suitable for writing to an SD card and placed in the Trimslice's Full Size SD slot (Front slot)
 and booting without further modification.
 Write with xzcat file.xz > /dev/mmcblkX, put in the device, and you're ready to go. Boots to a serial console.

 Most of the SD card images can be used with a USB storage device drive using the following method:
 Write the image to both the USB storage device and an SD card. IE, write the image using xzcat file.xz > /dev/sdX then xzcat file.xz > /dev/mmcblkX.
 Once written, use a partition editor such as fdisk to delete the VFAT partition from the USB drive and the Linux partition from SD card.
 Plug the SD and USB storage into your ARM device and power up. 
 The ARM system will load any applicable bootloader pieces, kernel, and initramfs from the SD card, but use the USB storage for the root filesystem.
 
 Nearly images are self-sufficient, but a kernel tarball is optionally available with the contents of the image's /boot and /lib/modules directories.
 These can be used in conjunction with the tarball root filesystems to create your own images.

=====Resizer=====
*Resizer Script and systemd file
:http://scotland.proximity.on.ca/fedora-arm/rootfs-resize/rootfs-resize-0.3/
:expects 2 partitions on SD card; will not work if a 3rd exists
:http://scotland.proximity.on.ca/arm-nightlies/vault/mknightly.tar.xz

====Archlinux-TrimSlice====
*http://archlinuxarm.org/platforms/armv7/trimslice

===RPi===
*Raspberry Hub WIKI: http://elinux.org/RaspberryPiBoard
:Good overview of RaspberryPi
*http://zenit.senecac.on.ca/wiki/index.php/Fedora_ARM_Secondary_Architecture
*element 14-Specs and Software List: http://www.element14.com/community/groups/raspberry-pi
:Order Page: http://www.newark.com/jsp/search/productdetail.jsp?SKU=83T1943
* Pi: Operating Systems Development! Course: http://www.cl.cam.ac.uk/freshers/raspberrypi/tutorials/os/
*Software: http://www.raspberrypi.org/downloads
*RPi Store: http://store.raspberrypi.com/ NEW
:http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix
:http://elinux.org/RaspberryPiBoard#Software_.26_OS_Distribution
:http://elinux.org/RPi_Distributions#What_is_armhf
*http://www.raspberrypi.org/archives/2221  
 "...BCM2835 used in the Raspberry Pi is the first ARM-based multimedia SoC with fully-functional,
 vendor-provided (as opposed to partial, reverse engineered) fully open-source drivers,..."
*Quick Start Guide:http://www.raspberrypi.org/quick-start-guide
*http://www.raspbian.org/
*http://www.raspbian.org/RaspbianImages
*http://www.memetic.org/pre-compiled-xbmc-for-raspbian/
*http://michael.gorven.za.net/blog/2012/08/06/xbmc-packages-raspberry-pi-running-raspbian
*http://elinux.org/R-Pi_Hub
*http://elinux.org/RPi_config.txt - How to set Overclocking / Video on RPi
*http://elinux.org/RPi_Performance
*http://elinux.org/RPi_Distributions#Comparison
:RPi resolution fix:"disable_overscan=1"
*http://elinux.org/RPi_VerifiedPeripherals#Working_USB_Wifi_Adapters
*fedora 17 Remix:ftp://ftp.ges.redhat.com/raspberrypi/test-releases/raspberrypi-fedora-remix-17/
*R-PI can use three different "memory models", that is splits of the 256MB RAM
:http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=4691
*RPi Configuration:http://elinux.org/RPiconfig
*RPi Troubleshooting
:http://elinux.org/R-Pi_Troubleshooting
:http://rpmfusion.org/Architectures/ARM
*Chromium Browser for RPi (beta)
:http://hexxeh.net/?p=328117859
*Update and install software before flashing .img using chroot
:http://raspberrypi.stackexchange.com/questions/855/is-it-possible-to-update-upgrade-and-install-software-before-flashing-an-image
====Kernel Testing====
*https://fedoraproject.org/wiki/Architectures/ARM/Quality_Assurance/Kernel_Testing
====Kernel Compilation====
*http://elinux.org/RPi_Kernel_Compilation
=====raspberry-pi-root-fs-on-usb-drive=====
*http://mitchtech.net/raspberry-pi-root-fs-on-usb-drive/
=====Xorg and LXDE===== 
:http://www.raspbian.org/PiscesImages

=====Mate on RPi=====
: http://www.raspbian.org/RaspbianMate
::DL: http://www.raspbian.org/PiscesMATEImages

===[[Testing/Reports|Testing Pages]]===
:List of Test Pages
====[[Testing|Testing Introductory Page]]====
:Help/Info Wiki Page
====[[Testing/Reports/ARM_RPi|Tests of f17-fedora-remix; Raspbian-PiscesMATE; and rasbian debian on RPi]]====
:http://scotland.proximity.on.ca/raspberrypi/test-releases/rpfr17/
:http://www.raspbian.org/PiscesMATEImages
:http://downloads.raspberrypi.org/images/raspbian/2012-07-15-wheezy-raspbian/2012-07-15-wheezy-raspbian.zip

====[[Testing/Reports/Sweets_on_Raspberry_pi_armhf_raspbian|Testing Sweets on a RPi armhf]]====
*Install of Sweets Sugar 0.94 on a RPi

===xmbc===
*http://www.memetic.org/pre-compiled-xbmc-for-raspbian/
===Gentoo===
*http://wiki.gentoo.org/wiki/Raspberry_Pi
===Mageia-arm===
 This ARM port supports the Kirkwood series from Marvell.
 Most frequent are: Open-RD, computer plugs (SheevaPlug, GuruPlug).
 It runs also in qemu as a virtual machine.
*http://blog.mageia.org/en/2011/06/23/arm-port-preview/
:Install to QEMU: http://packages.rtp-net.org/mageia/1/armv5tl/docs/README.ARMv5TL
:Prebuilt Images: http://packages.rtp-net.org/mageia/1/imgs/

==PPC==
:Power PC
* [[Ubuntu/PPC]]
* http://fedoraproject.org/wiki/Architectures/PowerPC
*: Latest Fedora release for PPC is currently Fedora 12
::Doing builds again for fedora 16
*: IRC: #fedora-ppc on irc.freenode.net
===Chromebook===
*Original writeup: https://plus.google.com/109993695638569781190/posts/b2fazijJppZ
====[http://www.chromestory.com/2012/11/install-fedora-17-on-samsung-chromebook-series-3-arm/ fedora-17-on-samsung-chromebook-series-3-arm]====
: EXPERIMENTAL run fedora 17 on Chromebook
*Note danger of blowing out the speakers.
====[https://plus.google.com/u/0/109993695638569781190/posts/34PYU79eUqP Building your own kernel and installing it in the Chromebook]====

====[http://support.google.com/chromeos/bin/answer.py?hl=en&answer=1080595 Recover your Chrome device]====
Install a new version of the Chrome operating system on your Chrome device by going through the recovery process. You may want to go through this process if you’re having problems updating your Chrome device or if your Chrome device stops working.
*Recovery: http://support.google.com/chromeos/bin/answer.py?hl=en&answer=1080595
====[https://fedoraproject.org/wiki/Architectures/ARM/Samsung_Chromebook_2012 fedora on a chromebook]====
*NEW--[[User:Satellit|Satellit]] 01:57, 6 December 2012 (EST)
====[http://chromeos-cr48.blogspot.com/2012/10/arm-chrubuntu-1204-alpha-1-now.html Chrubuntu-1204]====
*ChrUbuntu 12.04 for the new Google Chromebook with ARM processor! 
====[[Talk:Sugar_Creation_Kit/sck/Advanced_Topics |Ubuntu on Chromebook]]====
*https://plus.google.com/109993695638569781190/posts/b2fazijJppZ
*https://sites.google.com/a/chromium.org/dev/
*http://liliputing.com/2012/10/samsungs-arm-powered-chromebook-can-run-ubuntu.html
:http://www.samsung.com/global/business/semiconductor/minisite/Exynos/products5dual.html
:http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=4917324

====[https://wiki.debian.org/InstallingDebianOn/Samsung/ARMChromebook Debian on chromebook]====

*Entering Developer Mode
:http://goo.gl/TSZxs
 "On this device, both the recovery button and the dev-switch have been virtualized.
 Our partners don't really like physical switches - they cost money, take up space on the motherboard, and require holes in the case.
 To invoke Recovery mode, you hold down the ESC and Refresh keys and poke the Power button.
 To enter Dev-mode you first invoke Recovery, and at the Recovery screen press Ctrl-D (there's no prompt - you have to know to do it).
 It will ask you to confirm, then reboot into dev-mode.
 Dev-mode works the same as always: It will show the scary boot screen and you need to press Ctrl-D or wait 30 seconds to continue booting.
 You'll still have to run "crossystem dev_boot_usb=1" and reboot once to boot from USB drives with Ctrl-U. 
 To leave Dev-mode and go back to normal mode, just follow the instructions at the scary boot screen. It will prompt you to confirm.
 If you want to leave Dev-mode programmatically, you can run "crossystem disable_dev_request=1; reboot" from a root shell  .
 Th ere's no way to enter Dev-mode programmatically, and just seeing the Recovery screen isn't enough -  
 you have to use the three-finger salute which hard-resets the machine first.
  That's to prevent a remote attacker from tricking your machine into dev-mode without your knowledge.
 An unrelated note: Holding just Refresh and poking the Power button hard-resets the machine without entering Recovery.
  That's occasionally useful, but use it with care - it doesn't sync the disk or shut down politely,
  so there's a nonzero chance of trashing the contents of your stateful partition."

====gitweb====
*http://git.chromium.org/gitweb/
*https://code.google.com/p/git-repo/

====fedora====
*TESTING Section
* Hope to install Fedora on it.--[[User:Satellit|Satellit]] 02:32, 26 October 2012 (EDT)
*IRC #fedora-arm  freenode 
====openSUSE====
* IRC #opensuse-arm on freenode
*http://www.muktware.com/4655/opensuse-running-249-google-chromebook#.UIotWdEhjY5
:Detailed instructions: https://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ
=====opensuse-on-arm-release-candidate-1=====
:http://news.opensuse.org/2012/10/01/announcing-opensuse-on-arm-release-candidate-1/
:http://download.opensuse.org/repositories/openSUSE:/12.2:/ARM:/Contrib:/Origen/images/

==[[Sugar_on_a_Stick_Parallels| SoaS in Parallels for OS X]]==
::(experimental)
:: (Not very current)
==Sugar Patches==
:http://patchwork.sugarlabs.org/project/sugar/list/