			Virtual Network Computing
                                  from ORL

		    From VNC official documentation
		   ================================

   VNC consists of two types of component.  A server, which generates a
   display, and a viewer, which actually draws the display on your
   screen.   There are two important features of VNC:
     * The server and the viewer  may be on different machines and on
       different architectures.  We expect the most common use to be the
       display of a Unix X desktop on a PC, for example.  The protocol
       which connects the server and viewer is simple, open, and
       platform- independent.
     * No state is stored at the viewer. Breaking the viewer's connection
       to the server and then reconnecting will not result in any loss of
       data.  Because the connection can be remade from somewhere else,
       you have easy mobility.

  So, to get started with VNC you need to run a server, and then connect
   to it with a viewer.  There is a Windows server, WinVNC, but for the
   purposes of this introduction we will use the X-based server, Xvnc, so
   you will need access to a Unix machine. WinVNC is actually simpler -
   you just run it on one machine and then tell the viewer  to connect to
   this machine - but it has some limitations, so we'll start with X.
   The current VNC software requires a TCP/IP connection between the
   server and the viewer, though there is no reason why the software
   for example, RS232 or Firewire.  We have
   internal versions that use other network transport layers.

			 Using VNC in muLinux
		 	 =====================

Starting the server
------------------
		
			# vnc start

"vnc" search for a unused TCP port in >5900 range and assign the socket.
5900 correspond to display :0, 5901 to display :1, and so on.
Default display :1.
Many instance of Xvnc can run simulaneously. 

Look at the report messages!

Stopping the server
-------------------

			# vnc stop

Starting the client
-------------------- 

		# vnc some_host:0	{ connect to VNC server
				   	on host "some_host", display 0}
		# vnc localhost:1	{ connect to local VNC
					  X server, display 1}

See "svncviewer -h" (svgalib client) and "vncviewer -h" (X client):

If you use the "vnc" command in a Linux console, the
svncviewer (svgalib client) will be used. If, as alternative, you
use the "vnc" in a Xterm console under XWindow, the vncviewer 
(X client) will takes place. 

Connect to muLinux VNC server from a remote computer
running Windows
-----------------------------------------------------

Download a VNC client for Windows 9x/NT.

Alternatively, run a Java capable internet browser and point to URL

		http://mulinux-p-address:5801/

If muLinux VNC server run on display 2, uses the port 5802 instead,
and so on.


The muLinux SVGALIB client 
--------------------------

If you plan to use the VNC client in a muLinux text console, you must
disable "history" in the shell. 

		# setup -f misc	{answer n to ILE hystory}
		# leave the shell
		# re-authenticate

Finally, customize /etc/vga/libvga.config to reflect your video card,
mouse etc, uncommenting the right row.

Problems
-----

- Only standard keymap are supported.
- svncviewer work if video card is know by svgalib (the BIG problem).
