Chico2 desktop machine configuration - Revision history

Giovanni Saponaro: update links

2014-11-14T17:43:16Z

update links

← Older revision		Revision as of 17:43, 14 November 2014
Line 1:		Line 1:
	''July 2009 note: this page is obsolete! Chico2 is no longer being used as the machine that manages VisLab demos~~. A laptop called Chico3 does this, now~~. Please refer to the following page for more up-to-date configuration information: [[~~Chico3~~ laptop ~~machine configuration~~]].''		''July 2009 note: this page is obsolete! Chico2 is no longer being used as the machine that manages VisLab demos. Please refer to the following page for more up-to-date configuration information: [[iCub laptop]].''

	== Operating system installation ==		== Operating system installation ==

Giovanni Saponaro: this page is obsolete

2012-03-09T16:37:49Z

this page is obsolete

← Older revision		Revision as of 16:37, 9 March 2012
Line 1:		Line 1:
	''July 2009 note: Chico2 is no longer being used as the machine that manages VisLab demos. A laptop called Chico3 does this, now. Please refer to the following page for more up-to-date configuration information: [[Chico3 laptop machine configuration]].''		''July 2009 note: this page is obsolete! Chico2 is no longer being used as the machine that manages VisLab demos. A laptop called Chico3 does this, now. Please refer to the following page for more up-to-date configuration information: [[Chico3 laptop machine configuration]].''

	== Operating system installation ==		== Operating system installation ==

Giovanni Saponaro: add note explaining that Chico2 is no longer the demo machine. Link to Chico3 page

2009-07-08T10:31:52Z

add note explaining that Chico2 is no longer the demo machine. Link to Chico3 page

← Older revision		Revision as of 10:31, 8 July 2009
Line 1:		Line 1:
			''July 2009 note: Chico2 is no longer being used as the machine that manages VisLab demos. A laptop called Chico3 does this, now. Please refer to the following page for more up-to-date configuration information: [[Chico3 laptop machine configuration]].''

	== Operating system installation ==		== Operating system installation ==

Giovanni Saponaro: /* Customization of GNOME panel */ s/demo/icub/g;

2009-06-08T14:36:00Z

Customization of GNOME panel: s/demo/icub/g;

← Older revision		Revision as of 14:36, 8 June 2009
Line 183:		Line 183:
	click on the icon and select the directory where your icons are, typically ~/Pictures/		click on the icon and select the directory where your icons are, typically ~/Pictures/
	click on open, then select the picture for this particular button		click on open, then select the picture for this particular button
	write in the field "command": gnome-terminal --window-with-profile=cortex -e "ssh ~~demo~~@10.10.1.1 -X"		write in the field "command": gnome-terminal --window-with-profile=cortex -e "ssh icub@10.10.1.1 -X"
	set the name to something like: ssh ~~demo~~@cortex1		set the name to something like: ssh icub@cortex1
	the profile specified (--window-with-profile=cortex) does not exist by default, you need to create it.		the profile specified (--window-with-profile=cortex) does not exist by default, you need to create it.
	those profiles are used to give terminals on different machines different colors (e.g. all terminals running in a cortex computer will be blue, terminals local to chico2 will be white, etc.).		those profiles are used to give terminals on different machines different colors (e.g. all terminals running in a cortex computer will be blue, terminals local to chico2 will be white, etc.).
Line 196:		Line 196:
	* for the buttons that start nautilus, the file manager, on pc104 and on cortex (once again, all cortex computers share the same disk, so you need only one button for them) you should use these lines of code:		* for the buttons that start nautilus, the file manager, on pc104 and on cortex (once again, all cortex computers share the same disk, so you need only one button for them) you should use these lines of code:
	nautilus sftp://icub@10.10.1.50/home/icub/		nautilus sftp://icub@10.10.1.50/home/icub/
	nautilus sftp://~~demo~~@10.10.1.1/home/demo		nautilus sftp://icub@10.10.1.1/home/demo

	and... you're done!		and... you're done!

Giovanni Saponaro: /* Network */ add icubbrain{1,2} rack IPs in /etc/hosts

2009-06-05T18:19:56Z

Network: add icubbrain{1,2} rack IPs in /etc/hosts

← Older revision		Revision as of 18:19, 5 June 2009
Line 54:		Line 54:
	10.10.1.4 cortex4		10.10.1.4 cortex4
	10.10.1.5 cortex5		10.10.1.5 cortex5
			10.10.1.41 icubbrain1
			10.10.1.42 icubbrain2

	=== Additional packages ===		=== Additional packages ===

Giovanni Saponaro: /* Network */ add chico3 in /etc/hosts

2009-05-28T18:52:11Z

Network: add chico3 in /etc/hosts

← Older revision		Revision as of 18:52, 28 May 2009
Line 48:		Line 48:
	10.10.1.51 icubsrv		10.10.1.51 icubsrv
	10.10.1.52 chico2		10.10.1.52 chico2
			10.10.1.53 chico3 ''<-- this used to be venus' IP; not anymore''
	10.10.1.1 cortex1		10.10.1.1 cortex1
	10.10.1.2 cortex2		10.10.1.2 cortex2

Giovanni Saponaro: /* Ubuntu installation parameters */ always use icub user

2009-05-28T17:27:35Z

Ubuntu installation parameters: always use icub user

← Older revision		Revision as of 17:27, 28 May 2009
Line 19:		Line 19:
	machine name: chico2		machine name: chico2

	user name: vislab ~~(we might need a~~ user ~~icub in the future~~ for ~~"yarp run" operations since~~ the pc104 only has user icub ~~as a permanent one~~)		user name: icub (don't use vislab user, as for demos yarprun requires all users to be called the same, and pc104 only has a 'icub' user - therefore, always use icub on chico2 too)

	=== Operations after first boot ===		=== Operations after first boot ===

Giovanni Saponaro: /* Customization of GNOME panel */ update link

2009-05-28T16:08:28Z

Customization of GNOME panel: update link

← Older revision		Revision as of 16:08, 28 May 2009
Line 168:		Line 168:
	== Customization of GNOME panel ==		== Customization of GNOME panel ==

	''See [[Chico2 machine configuration/Archive]] for obsolete information. Here we report how we actually proceeded.''		''See [[Chico2 desktop machine configuration/Archive]] for obsolete information. Here we report how we actually proceeded.''

	* add buttons to the panel/bar at the top of the screen, to conveniently open terminals and file managers on remote machines.		* add buttons to the panel/bar at the top of the screen, to conveniently open terminals and file managers on remote machines.

Giovanni Saponaro: Chico2 machine configuration moved to Chico2 desktop machine configuration: specify in title that this machine is a desktop (as opposed to the laptops attached to Chico)

2009-05-28T16:07:07Z

Chico2 machine configuration moved to Chico2 desktop machine configuration: specify in title that this machine is a desktop (as opposed to the laptops attached to Chico)

← Older revision	Revision as of 16:07, 28 May 2009
(No difference)

Giovanni Saponaro: /* More VisLab-specific configuration */ overriding pc104 RSA key error

2009-05-27T10:56:40Z

More VisLab-specific configuration: overriding pc104 RSA key error

← Older revision		Revision as of 10:56, 27 May 2009
Line 162:		Line 162:
	#rm the id_rsa.pub file		#rm the id_rsa.pub file
	rm id_rsa.pub		rm id_rsa.pub
	~~#restart~~ pc104 and check that you can log in passwordlessly.
			Restart pc104 and check that you can log in passwordlessly. If you receive an RSA key error because of different pc104 hardware setups (with or without pen), thus different RSA keys, you can use this option:
			ssh -o StrictHostKeyChecking=no pc104

	== Customization of GNOME panel ==		== Customization of GNOME panel ==