1. retrieve IP address of your PI -your server in this case

   1 2 3

   ip addr

2. access your PI from another issue with your vnc client from another PC, smart phone or Chrome VNCviewer

3. On the server side -your pi

   1 2 3 4

   vncserver:1   #from 5901 port,  OR the following vncserver -geometry 1440x900 -alwaysshared -dpi 96 :1

   input password when asked, or change later with vncpasswd

4. On the client side

   1 2 3

   vncviewer localhost::8900 or ip, OR fill in the GUI

5. Starting and stopping vncserver at bootup and shutdown via systemd Create /etc/systemd/system/vncserver@:1.service and modify it defining the user to run the server. Use this with systemd to manage it. Here is the file origin [/lib/systemd/system/vncserver@.service]

   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

   # The vncserver service unit file # The vncserver service unit file # # 1. Copy this file to /etc/systemd/system/vncserver@:<display>.service # 2. Edit User= #   ("User=foo") # 3. Edit  and vncserver parameters appropriately #   ("/usr/bin/vncserver %i -arg1 -arg2 -argn") # 4. Run `systemctl daemon-reload` # 5. Run `systemctl enable vncserver@:<display>.service` # # DO NOT RUN THIS SERVICE if your local area network is untrusted! # # See the wiki page for more on security # https://wiki.archlinux.org/index.php/Vncserver   [Unit] Description=Remote desktop service (VNC) After=syslog.target network.target   [Service] Type=simple User= PAMName=login   # Clean any existing files in /tmp/.X11-unix environment ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :' ExecStart=/usr/bin/vncserver -geometry 1440x900 -fg -alwaysshared -dpi 100 %i ExecStop=/usr/bin/vncserver -kill %i   [Install] WantedBy=multi-user.target

6. The screen capture.

   

7. In Debian system, follow instruction here.

1. invoke like this

   1 2 3

   $ x0vncserver -display :0 -passwordfile ~/.vnc/passwd

   Note: use passwd to change or set password

2. Starting and stopping x0vncserver via systemd Note: This unit will only be useful if the user in the unit is currently running a X session. In order to have a VNC Server runnning x0vncserver, which is the easiest way for most users to quickly have remote access to the current desktop, you can create a systemd unit. Create /etc/systemd/system/x0vncserver.service and modify it defining the user to run the server, and the desired options. /etc/systemd/system/x0vncserver.service

   1 2 3 4 5 6 7 8 9 10 11 12 13

   [Unit] Description=Remote desktop service (VNC) After=syslog.target network.target   [Service] Type=forking User=foo ExecStart=/usr/bin/sh -c '/usr/bin/x0vncserver -display :0 -rfbport 5900 -passwordfile /home/foo/.vnc/passwd &'   [Install] WantedBy=multi-user.target

The concept is to share your laptop keyboard and screen with Raspberry PI with xforwarding or VNC via network bridging. All you need is an ethernet cable (crossover is not necessary for most cases). Both systems can share your laptop wireless internet.

This does not belong here, but it is really cool stuff. Mosh is cooler, but does not work with x-forwarding yet.

1. make changes to /etc/ssh/sshd_config [NOT ssh_config] by un-commenting following lines

   1 2 3 4 5

   X11Forwarding yes X11DisplayOffset 10 X11UseLocalhost yes

   Note make changes to ssh_config will disable sshd connection

2. restart sshd and checking status

   1 2 3 4

   sudo systemctl restart sshd sudo systemctl status sshd

3. ssh -X from another computer

   1 2 3

   ssh -X user@ip

   and, start any gui application,

4. Some notes from my side:
   1. only terminal needed from host side
   2. on client side, Xlib RAND and SYNC warning shows up, but works regardless, possible solution here.
   3. use ssh -Y without any warning

Followed up the instruction here, does not really work. stopped at brctl addif bridgename eth0, did not get a chance to figure out why. what worked for me is using network manager, and set as as following from your linux PC.

Notes: Above worked fine with Rasbian too; VNC and ssh both worked fine with me.

https://www.google.com/search?q=science+news&ie=utf-8&oe=utf-8#q=science+news&start=10 Procedures:

1. start up Raspberry Pi and Laptop running Arch Linux
2. Connect RasPI (server) with PC (client) with an ethernet cable.

3. Locate the ip for Raspi from PC -client

   1 2 3

   ip neighbour

4. The No description for this link way

   1. SSH to RasPi and turn on VNC server
   1 2 3 4

   ssh tan@ip vncserver

   2). vnc or “SSH -X” back to Raspi from laptop

   1 2 3

   vncviewer ip:5901

5. OR, set up rasPI the No description for this link local display way, and vnc or ssh -X to it
6. Fix for no mouse cursor

If no mouse cursor is visible when using x0vncserver, start vncviewer as follows:

Or put DotWhenNoCursor=1 in the tigervnc configuration file, which is at ~/.vnc/default.tigervnc by default in your client PC, not rasPi.