Skip to main content

Remote Desktop Using Tightvnc

Since Slackware 13.0, tightvnc package has been added to the repository, even though it still resides in extra/ directory, meaning it's not yet in the main directory. No problems though, since it's quite stable enough for daily usage and i will show you how to use it.

First of all, tightvnc is an application which allows you to control your other computer (desktop/laptop) via a network. It's different compared to normal ssh connection, since you will have full access to your desktop, but it's same with SSH X11 Forwarding but with less configuration (IMHO) Yahoo

OK, let's start the very simple tutorial. Install tightvnc package by issuing installpkg tightvnc-1.3.10-i486-1.txz or slackpkg install tightvnc if you are using slackpkg. This will install a vncserver (server) and vncviewer (client) components.

SERVER
All you need on the server is to run the vncserver application with some configuration. The most basic configuration is by running
vncserver -geometry 1024x768
this will run the vncserver in background, listening for incoming connection from vncclient and setting the screen as 1024x768 (change this to your resolution). You can view other options by issuing man vncserver. Don't forget to add a strong password so that it will give you extra protection to your computer.

Here's an example:

willysr@desktop:~$ vncserver -geometry 1024x768

You will require a password to access your desktops.

Password:
Verify:
Would you like to enter a view-only password (y/n)? n

New 'X' desktop is desktop:1

Creating default startup script /home/willysr/.vnc/xstartup
Starting applications specified in /home/willysr/.vnc/xstartup
Log file is /home/willysr/.vnc/desktop:1.log

Remember the display part. You will need them to access your server. In this case, it's 1 (desktop:1).

CLIENT
In order to access the computer, run vncviewer and enter the IP address of the computer along with the display number. For example, if other computer is running on 192.168.1.2 and the display number is 1, you entered 192.168.1.2:1. Enter the password that you have set up before and if you are authenticated, you will have full access of your other computer in your current computer.

If you want to have fullscreen access, you can pass -fullscreen into the vncviewer command.

Here's an example of tightvnc in action from Slackware-Current to Ubuntu Lucid Lynx 10.04 Beta 2

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called rsync_current.sh and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on 192.168.1.1 and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue