ICub laptop - Revision history

Giovanni Saponaro: /* NFS */ fix formatting

2017-11-20T17:08:11Z

NFS: fix formatting

← Older revision		Revision as of 17:08, 20 November 2017
Line 39:		Line 39:

	Notes about the NFS client configuration:		Notes about the NFS client configuration:
	# we specify the IP address of the server rather than its name: for example, ''10.10.1.53:/exports/code'' rather than ''icub-laptop:/exports/code''		# we specify the IP address of the server rather than its name: for example, <code>10.10.1.53:/exports/code</code> rather than <code>icub-laptop:/exports/code</code>
	# we enforce NFSv3 to fix a problem related to automatic mounting on boot		# we enforce NFSv3 to fix a problem related to automatic mounting on boot

Giovanni Saponaro: /* NFS */ fix IP addresses and formatting

2017-11-20T17:07:41Z

NFS: fix IP addresses and formatting

← Older revision		Revision as of 17:07, 20 November 2017
Line 35:		Line 35:

	NFS client configuration: the shared volumes are defined in '''/etc/fstab''' as follows.		NFS client configuration: the shared volumes are defined in '''/etc/fstab''' as follows.
	~~icub-laptop~~:/exports/code /usr/local/src/robot nfs _netdev,auto,hard,intr,nfsvers=3 0 0		10.10.1.53:/exports/code /usr/local/src/robot nfs _netdev,auto,hard,intr,nfsvers=3 0 0
	~~icub-laptop~~:/exports/local_yarp /home/icub/.local/share/yarp nfs _netdev,auto,hard,intr,nfsvers=3 0 0		10.10.1.53:/exports/local_yarp /home/icub/.local/share/yarp nfs _netdev,auto,hard,intr,nfsvers=3 0 0

	Notes about the NFS client configuration:		Notes about the NFS client configuration:
	# we specify the IP address of the server rather than its name: for example, `10.10.1.53:/exports/code` rather than `icub-laptop:/exports/code`		# we specify the IP address of the server rather than its name: for example, ''10.10.1.53:/exports/code'' rather than ''icub-laptop:/exports/code''
	# we enforce NFSv3 to fix a problem related to automatic mounting on boot		# we enforce NFSv3 to fix a problem related to automatic mounting on boot

Giovanni Saponaro: /* NFS */

2017-11-20T16:56:03Z

NFS

← Older revision		Revision as of 16:56, 20 November 2017
Line 40:		Line 40:
	Notes about the NFS client configuration:		Notes about the NFS client configuration:
	# we specify the IP address of the server rather than its name: for example, `10.10.1.53:/exports/code` rather than `icub-laptop:/exports/code`		# we specify the IP address of the server rather than its name: for example, `10.10.1.53:/exports/code` rather than `icub-laptop:/exports/code`
	# we enforce NFSv3 to fix a problem ~~relating~~ to automatic mounting on boot		# we enforce NFSv3 to fix a problem related to automatic mounting on boot

	Successful mounting on client machines shows something link this (where 10.10.1.x is the client IP):		Successful mounting on client machines shows something link this (where 10.10.1.x is the client IP):

Giovanni Saponaro: /* NFS */ enforce NFSv3, improve documentation

2017-11-20T16:55:33Z

NFS: enforce NFSv3, improve documentation

← Older revision		Revision as of 16:55, 20 November 2017
Line 30:		Line 30:
	== NFS ==		== NFS ==

	~~These~~ NFS ~~filesystems are exported according to~~ '''/etc/exports''':		NFS server configuration: the volumes must be defined in '''/etc/exports''' as follows.
	/exports/code 10.10.1.0/255.255.255.0(rw,sync,no_root_squash,no_subtree_check)		/exports/code 10.10.1.0/255.255.255.0(rw,sync,no_root_squash,no_subtree_check)
	/exports/local_yarp 10.10.1.0/255.255.255.0(rw,sync,no_root_squash,no_subtree_check)		/exports/local_yarp 10.10.1.0/255.255.255.0(rw,sync,no_root_squash,no_subtree_check)

	~~The~~ NFS ~~filesystems~~ are ~~mounted as~~ defined in '''/etc/fstab''':		NFS client configuration: the shared volumes are defined in '''/etc/fstab''' as follows.
	icub-laptop:/exports/code /usr/local/src/robot nfs _netdev,auto,hard,intr 0 0		icub-laptop:/exports/code /usr/local/src/robot nfs _netdev,auto,hard,intr,nfsvers=3 0 0
	icub-laptop:/exports/local_yarp /home/icub/.local/share/yarp nfs _netdev,auto,hard,intr 0 0		icub-laptop:/exports/local_yarp /home/icub/.local/share/yarp nfs _netdev,auto,hard,intr,nfsvers=3 0 0

			Notes about the NFS client configuration:
			# we specify the IP address of the server rather than its name: for example, `10.10.1.53:/exports/code` rather than `icub-laptop:/exports/code`
			# we enforce NFSv3 to fix a problem relating to automatic mounting on boot

	Successful mounting on client machines shows something link this (where 10.10.1.x is the client IP):		Successful mounting on client machines shows something link this (where 10.10.1.x is the client IP):

Giovanni Saponaro: /* Specifications */ more informative Nvidia specifications

2016-05-09T11:33:21Z

Specifications: more informative Nvidia specifications

← Older revision		Revision as of 11:33, 9 May 2016
Line 9:		Line 9:
	* processor: 4 x [http://ark.intel.com/products/75117/ i7-4700MQ] @ 2.40-3.40 GHz		* processor: 4 x [http://ark.intel.com/products/75117/ i7-4700MQ] @ 2.40-3.40 GHz
	* memory: 32GB		* memory: 32GB
	* graphics card: Nvidia GeForce GTX 770M with ~~CUDA and~~ 3072MB of memory; onboard card HD 4600		* graphics card: Nvidia GeForce GTX 770M (compute capability 3.0) with 3072MB of memory; onboard card HD 4600

	= Setup =		= Setup =

Giovanni Saponaro at 13:15, 12 February 2015

2015-02-12T13:15:22Z

← Older revision		Revision as of 13:15, 12 February 2015
Line 21:		Line 21:
	== Network ==		== Network ==

	''See also [[~~VisLab~~ machines configuration#Network_configuration]]''.		''See also [[iCub machines configuration#Network_configuration]]''.

	address 10.10.1.53		address 10.10.1.53

Giovanni Saponaro: cleanup

2015-02-10T16:39:06Z

cleanup

← Older revision		Revision as of 16:39, 10 February 2015
Line 66:		Line 66:

	* we can log onto other machines only when NFS volumes have been successfully mounted (when icub-laptop is up) - insert a robust mechanism (e.g. timeout) to let us log anytime		* we can log onto other machines only when NFS volumes have been successfully mounted (when icub-laptop is up) - insert a robust mechanism (e.g. timeout) to let us log anytime

	~~= Additional software =~~

	= Customization =		= Customization =

Giovanni Saponaro: /* Additional software */ cleanup

2015-02-10T16:38:33Z

Additional software: cleanup

← Older revision		Revision as of 16:38, 10 February 2015
Line 68:		Line 68:

	= Additional software =		= Additional software =

	~~== Nvidia graphics card ==~~

	~~== YARP and iCub ==~~

	= Customization =		= Customization =

Giovanni Saponaro: simplify; working icon launchers

2015-02-02T18:53:44Z

simplify; working icon launchers

← Older revision		Revision as of 18:53, 2 February 2015
Line 49:		Line 49:

	If automatic mounting at boot time fails, mount the volumes manually:		If automatic mounting at boot time fails, mount the volumes manually:
	sudo mount icub-laptop:/exports/code /usr/local/src/robot -t nfs -o _netdev,auto,hard,intr		sudo mount /usr/local/src/robot
	sudo mount icub-laptop:/exports/local_yarp /home/icub/.local/share/yarp -t nfs -o _netdev,auto,hard,intr		sudo mount /home/icub/.local/share/yarp
	~~# or simply (if the corresponding entries exist in /etc/fstab):~~		# the above commands use settings from /etc/fstab and are equivalent to:
	~~# sudo mount /usr/local/src/robot~~		# sudo mount icub-laptop:/exports/code /usr/local/src/robot -t nfs -o _netdev,auto,hard,intr
	~~# sudo mount /home/icub/.local/share/yarp~~		# sudo mount icub-laptop:/exports/local_yarp /home/icub/.local/share/yarp -t nfs -o _netdev,auto,hard,intr

	== Open issues ==		== Open issues ==
Line 84:		Line 84:

	== Launcher icons ==		== Launcher icons ==

			=== Bash script icons ===

			To create a launcher on the desktop, create a file with a <code>.sh</code> extension, make it executable and edit the content like this:

			#!/bin/bash
			source ~/.bash_iCubrc
			icub-cluster.py vislab-cluster.xml // <- customize this line with the command and arguments
			exec /bin/bash

			=== GNOME Panel icons ===

			'''Note: as of Feb. 2015 this method is broken due to [https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/378783 this bug] in GNOME.'''

	Install <code>gnome-panel</code> then use <code>gnome-desktop-item-edit</code> to create/edit launcher icons on the Desktop.		Install <code>gnome-panel</code> then use <code>gnome-desktop-item-edit</code> to create/edit launcher icons on the Desktop.

Giovanni Saponaro: /* Launcher icons */ add links to gnome bug (desktop launchers open in gedit instead of being executed) and possible workarounds

2015-02-02T13:57:49Z

Launcher icons: add links to gnome bug (desktop launchers open in gedit instead of being executed) and possible workarounds

← Older revision		Revision as of 13:57, 2 February 2015
Line 95:		Line 95:
	Comment: Launch iCub cluster manager (yarpserver and yarprun)		Comment: Launch iCub cluster manager (yarpserver and yarprun)

	~~Troubleshooting~~: in the ~~Xfce4 window manager (Xubuntu) clicking on~~ the ~~icons might produce these errors~~: ~~"There was an error launching the application" or "No running instance of xfce4~~-~~panel was found"~~. ~~Solution: tbd~~		More information and troubleshooting:
			* [https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/378783 xdg-open *.desktop opens text editor]
			* [http://askubuntu.com/questions/5172/running-a-desktop-file-in-the-terminal Running a .desktop file in the terminal]
			* [http://stackoverflow.com/questions/6020106/hashbang-for-gnome-desktop-files/ Hashbang for Gnome .desktop files]

	= See also =		= See also =