Development Team/Manual/Setup - Revision history

Quozl: /* Jabber Servers */

2017-08-14T04:26:38Z

Jabber Servers

@@ Line 215: / Line 215: @@
 * [[Activities]] -- can be downloaded using the built-in browser or installed from the command line
 * General Linux packages can be downloaded and installed using Yum (note, these changes will be wiped out on the next OS upgrade)
 === SSH Access ===

FGrose at 18:14, 3 July 2012

2012-07-03T18:14:03Z

← Older revision		Revision as of 14:14, 3 July 2012
Line 3:		Line 3:

	[[Image:Sugar.png\|right\|thumb\|Sugar GUI Shell (Our Goal)]]		[[Image:Sugar.png\|right\|thumb\|Sugar GUI Shell (Our Goal)]]
	The OLPC's software environment is a heavily modified [[~~Community/Distributions/Fedora\|~~ Fedora]] 11 Linux system running a custom [[Sugar\|GUI shell]] (Sugar). To develop for the platform you will eventually need access to a platform which runs in a manner substantially similar to the OLPC environment. To put it simply, you will likely need to have Sugar running on a computer.		The OLPC's software environment is a heavily modified [[Fedora]] 11 Linux system running a custom [[Sugar\|GUI shell]] (Sugar). To develop for the platform you will eventually need access to a platform which runs in a manner substantially similar to the OLPC environment. To put it simply, you will likely need to have Sugar running on a computer.

	There are two major approaches to running Sugar, running it natively on your machine, and running it in an emulated environment. Which approach you choose will depend on a number of factors, including:		There are two major approaches to running Sugar, running it natively on your machine, and running it in an emulated environment. Which approach you choose will depend on a number of factors, including:
Line 140:		Line 140:
	This is what the core development team uses and is one of the most pleasant ways to work (once set up). Compared with using an Emulated XO, installing sugar takes more time and space to set up, and can be difficult to maintain, but results in a more flexible environment.		This is what the core development team uses and is one of the most pleasant ways to work (once set up). Compared with using an Emulated XO, installing sugar takes more time and space to set up, and can be difficult to maintain, but results in a more flexible environment.

	The 'native' environment for sugar-jhbuild is [[~~Community/Distributions/Fedora\|~~Fedora]], and this is by far the best supported development platform for sugar-jhbuild. [[~~Community/Distributions/Ubuntu\|~~Ubuntu]] and [[~~Community/Distributions/Gentoo\|~~Gentoo]] can also build the environment.		The 'native' environment for sugar-jhbuild is [[Fedora]], and this is by far the best supported development platform for sugar-jhbuild. [[Ubuntu]] and [[Gentoo]] can also build the environment.

	Currently sugar-jhbuild requires about 2.5 hours to complete building on a modern workstation (AMD4800+).		Currently sugar-jhbuild requires about 2.5 hours to complete building on a modern workstation (AMD4800+).
Line 156:		Line 156:
	As Sugar stabilizes and is ported to more distributions, it should be possible to use your Linux distribution's package management system to install Sugar. Distributions with ports so far:		As Sugar stabilizes and is ported to more distributions, it should be possible to use your Linux distribution's package management system to install Sugar. Distributions with ports so far:

	* [[~~Community/Distributions/~~Ubuntu]] -- These packages seem to work well and are extremely easy to set up. If you are running on Ubuntu Gutsy and are not working on Sugar's core software, this is very simple way to work.		* [[Ubuntu]] -- These packages seem to work well and are extremely easy to set up. If you are running on Ubuntu Gutsy and are not working on Sugar's core software, this is very simple way to work.
	* [[~~Community/Distributions/~~Debian]]-- Note that we need more testing of this package-set, please let us know your experiences		* [[Debian]]-- Note that we need more testing of this package-set, please let us know your experiences

FGrose at 18:03, 3 July 2012

2012-07-03T18:03:39Z

Show changes

Quozl: refer to sugargame in pygame context

2011-01-19T04:44:16Z

refer to sugargame in pygame context

← Older revision		Revision as of 00:44, 19 January 2011
Line 200:		Line 200:
	* [[OLPC:Developers/Stack#Browser\|Browser]] -- Mozilla/Firefox-derived web browser		* [[OLPC:Developers/Stack#Browser\|Browser]] -- Mozilla/Firefox-derived web browser
	* [[OLPC:Developers/Stack#Etoys\|Etoys]] -- Squeak/Smalltalk multimedia environment		* [[OLPC:Developers/Stack#Etoys\|Etoys]] -- Squeak/Smalltalk multimedia environment
	* [[OLPC:Developers/Stack#OLPCGames\|Pygame]] -- raster-graphics game development framework		* [[OLPC:Developers/Stack#OLPCGames\|Pygame]] -- raster-graphics game development framework, see also [[Development_Team/Sugargame]]
	* [[OLPC:Developers/Stack#Flash\|Flash]] -- Gnash or Adobe-Flash engine		* [[OLPC:Developers/Stack#Flash\|Flash]] -- Gnash or Adobe-Flash engine

Quozl: /* SSH Access */

2011-01-03T22:47:44Z

SSH Access

← Older revision		Revision as of 18:47, 3 January 2011
Line 229:		Line 229:
	== SSH Access ==		== SSH Access ==

	You will often want to be able to use file-transfer and remote-login operations to access your Sugar environment. We ~~generally~~ recommend using ssh-based access for working with your Sugar environment remotely.		You will often want to be able to use file-transfer and remote-login operations to access your Sugar environment. We recommend using ssh-based access for working with your Sugar environment remotely.

	Note: If you are using sugar-jhbuild you likely do '''not''' need to follow these instructions (since you're already using a running Linux desktop that shares its login and file-system with the Sugar instance).		Note: If you are using sugar-jhbuild you likely do '''not''' need to follow these instructions (since you're already using a running Linux desktop that shares its login and file-system with the Sugar instance).
Line 240:		Line 240:
	=== Password Based ===		=== Password Based ===

	Password-based SSH authentication is convenient and simple to set up, ~~but~~ it is far easier to crack than key-based access. ~~Consider using~~ key-based authentication ~~unless~~ you are ~~absolutely sure~~ that ~~no-one can reach~~ your ~~Sugar environment from untrusted networks (and maybe even then~~).		Password-based SSH authentication is convenient and simple to set up.

			''(However, it is far easier to crack than key-based access. This is because a password can be guessed, especially if multiple automatic attacks are made. Attacks can arrive over a wireless network from hosts that you trust. It is more secure to use key-based authentication. Accept password-based authentication if you are confident that your network is secured.)''

	Open a [[OLPC:Terminal]] activity and run:		Open a [[OLPC:Terminal]] activity and run:
Line 246:		Line 248:
	passwd		passwd

	which will prompt you to enter a password (and confirm it).		which will prompt you to enter a password (and confirm it). This enables remote access for the default user.

	~~Note:~~ you ~~can~~ also set a password on the root account ~~by doing~~:		Since the default user can su, you should also set a password on the root account:

	su root		su root
	passwd		passwd

	~~in the terminal window. This is strongly recommended if you are going to allow remote access to your machine.~~

	=== SSH Key Based ===		=== SSH Key Based ===
Line 261:		Line 261:
	In summary, you create a private key which will be stored on your remote system and encrypted with a strong password. You transfer the public key (think of it as a lock) that corresponds to that key to the Sugar environment and install it as an "authenticated key" which can be used to log into the Sugar environment.		In summary, you create a private key which will be stored on your remote system and encrypted with a strong password. You transfer the public key (think of it as a lock) that corresponds to that key to the Sugar environment and install it as an "authenticated key" which can be used to log into the Sugar environment.

	On your remote system, install SSH (Linux and ~~MacOS~~ will already have it installed, on Windows use the PuTTY program) and generate a new ssh key pair (following is for Linux~~/MacOS~~, refer to PuTTY's documentation for details on Windows):		On your remote system, install SSH (Linux and Mac OS X will already have it installed, on Windows use the PuTTY program) and generate a new ssh key pair (following is for Linux and Mac OS X, refer to PuTTY's documentation for details on Windows):

	ssh-keygen		ssh-keygen
Line 269:		Line 269:
	* Accept the defaults for key-type and size.		* Accept the defaults for key-type and size.
	* If ssh-keygen asks if you want to overwrite a key say '''No''', you are about to destroy your current ssh key!		* If ssh-keygen asks if you want to overwrite a key say '''No''', you are about to destroy your current ssh key!
	* Use a strong ~~pass-phrase~~ that you can remember easily (the ~~pass phrase~~ will need to be entered frequently unless you make use of an ~~ssh-~~agent such as offered by PuTTY or Gentoo's keychain)		* Use a strong passphrase that you can remember easily (the passphrase will need to be entered frequently unless you make use of an agent such as offered by PuTTY, ssh-agent or Gentoo's keychain)

	~~This~~ will normally create a file in your ~/.ssh/ directory named id_rsa.pub (if you accepted the defaults). ~~You now need to copy~~ this file to your Sugar environment and add it to the contents of ~~your~~ ~/.ssh/authorized_keys file (you may need to create the file).		''ssh-keygen'' will normally create a file in your ~/.ssh/ directory named id_rsa.pub (if you accepted the defaults). Copy this file to your Sugar environment and add it to the contents of the ~/.ssh/authorized_keys file (you may need to create the file).

	mkdir ~~~olpc~~/.ssh		mkdir ~/.ssh
	cat id_rsa.pub >> ~~~olpc~~/.ssh/authorized_keys		cat id_rsa.pub >> ~/.ssh/authorized_keys

	add your key to your keychain/ssh-agent application and you can now use SSH with just a single sign-on for many concurrent actions.		add your key to your keychain or ssh-agent application and you can now use SSH with just a single sign-on for many concurrent actions.

	See: [[OLPC:Emulating the XO/Help_and_tips#SSH into qemu\|SSH Into Qemu]] for Qemu-specific notes regarding port forwarding		See: [[OLPC:Emulating the XO/Help_and_tips#SSH into qemu\|SSH Into Qemu]] for Qemu-specific notes regarding port forwarding

Patrol: Reverted edits by Empress09 (talk) to last revision by Patrol

2010-05-12T06:25:45Z

Reverted edits by Empress09 (talk) to last revision by Patrol

← Older revision		Revision as of 02:25, 12 May 2010
Line 116:		Line 116:

	See Also:		See Also:
	* [http://www.lindaolsson.com/'''palm beach condo''']
	* [[#Configuration and Usage]] -- instructions on how to setup and use Sugar once you have it installed		* [[#Configuration and Usage]] -- instructions on how to setup and use Sugar once you have it installed

Vd026 at 04:09, 12 May 2010

2010-05-12T04:09:02Z

← Older revision		Revision as of 00:09, 12 May 2010
Line 116:		Line 116:

	See Also:		See Also:
			* [http://www.lindaolsson.com/'''palm beach condo''']
	* [[#Configuration and Usage]] -- instructions on how to setup and use Sugar once you have it installed		* [[#Configuration and Usage]] -- instructions on how to setup and use Sugar once you have it installed

Patrol: moved Walter is a wanker 12/Manual/Setup to Development Team/Manual/Setup over redirect: revert

2010-02-24T01:33:10Z

moved Walter is a wanker 12/Manual/Setup to Development Team/Manual/Setup over redirect: revert

← Older revision	Revision as of 21:33, 23 February 2010
(No difference)

Page move vandal: moved Development Team/Manual/Setup to Walter is a wanker 12/Manual/Setup: Walter is a wanker

2010-02-24T00:21:28Z

moved Development Team/Manual/Setup to Walter is a wanker 12/Manual/Setup: Walter is a wanker

← Older revision	Revision as of 20:21, 23 February 2010
(No difference)

Patrol: moved Anal bleaching 15/Manual/Setup to Development Team/Manual/Setup over redirect: revert

2010-02-21T22:42:02Z

moved Anal bleaching 15/Manual/Setup to Development Team/Manual/Setup over redirect: revert

← Older revision	Revision as of 18:42, 21 February 2010
(No difference)

← Older revision		Revision as of 00:44, 19 January 2011
Line 200:		Line 200:
	* [[OLPC:Developers/Stack#Browser\|Browser]] -- Mozilla/Firefox-derived web browser		* [[OLPC:Developers/Stack#Browser\|Browser]] -- Mozilla/Firefox-derived web browser
	* [[OLPC:Developers/Stack#Etoys\|Etoys]] -- Squeak/Smalltalk multimedia environment		* [[OLPC:Developers/Stack#Etoys\|Etoys]] -- Squeak/Smalltalk multimedia environment
	* [[OLPC:Developers/Stack#OLPCGames\|Pygame]] -- raster-graphics game development framework		* [[OLPC:Developers/Stack#OLPCGames\|Pygame]] -- raster-graphics game development framework, see also [[Development_Team/Sugargame]]
	* [[OLPC:Developers/Stack#Flash\|Flash]] -- Gnash or Adobe-Flash engine		* [[OLPC:Developers/Stack#Flash\|Flash]] -- Gnash or Adobe-Flash engine