xf4vnc |
xf4vnc features
* Works with the Xfree86 v4.x codebase, which means new extensions like RENDER and GLX (which means OpenGL(tm)) are supported. * All features from tightVNC 1.2.9 included, http://sf.net/projects/vnc-tight * Ability to deliver events upon connection or disconnecting VNC clients. * Provides a vnc.so to export your local console (aka :0) and the traditional Xvnc Xserver. * Fast OpenGL direct rendering on VNC clients using Chromium http://chromium.sf.net
xf4vnc as the drop in replacement for Xvnc
Download the Xvnc-4.3.0.x-<os>.gz file and unpack it with gunzip <filename>. Then run 'chmod +x' on that file to make it executable. This is now your Xserver. For more information on configuring Xvnc your probably better off looking at the tightVNC projects pages. Goto http://www.tightvnc.com. As for the vncviewer replacement, when specifying the modular encodings you need to add '.so' to load the real module. For example. vncviewer :1 -encodings "hextile.so copyrect.so"
xf4vnc for XFree86 exporting :0
To install using the automated method:
Download your appropriate package from the download section. Then unpack with 'tar xvzf pkgname.tar.gz' Finally run the provided 'install.sh' script for installation instructions which is fully automated. To install using a manual method:
* Copy the vnc.so-<os>-<version> to /usr/X11R6/lib/modules/vnc.so * Modify the XF86Config-4 (or XF86Config) with the modifications listed below...... * Make sure you use the Option 'usevnc' to actually enable VNC on that device!!!!!
NOTE: your XFree86.0.log file will produce errors regarding the loading of rfbkeyb and the rfbmouse drivers. This can safely be ignored as these drivers are embedded within the vnc.so binary. You'll get something like this... (II) LoadModule: "rfbmouse" (WW) Warning, couldn't open module rfbmouse (II) UnloadModule: "rfbmouse" (EE) Failed to load module "rfbmouse" (module does not exist, 0) (II) LoadModule: "rfbkeyb" (WW) Warning, couldn't open module rfbkeyb (II) UnloadModule: "rfbkeyb" (EE) Failed to load module "rfbkeyb" (module does not exist, 0) # Don't replace this section, add the the commands to your existing Section. Section "ServerLayout" .... InputDevice "vncMouse" "ExtraPointer" InputDevice "vncKeyboard" "ExtraKeyboard" .... EndSection # Don't replace this section, add the Load "vnc" line to your existing Section. Section "Module" ... Load "vnc" .... EndSection Section "InputDevice" # vncKeyboard: keyboard actions from vnc Identifier "vncKeyboard" Driver "rfbkeyb" EndSection Section "InputDevice" # vncMouse: mouse actions from vnc Identifier "vncMouse" Driver "rfbmouse" EndSection You can also use these options in your Device Section to enable other features. # rfb options # By default, no password is required. # The next rfbauth uses the root password for vncserver #Option "rfbauth" "/root/.vnc/passwd" Option "rfbport" "5900" # The use one of the next ...shared options ("nevershared" is the default) Option "nevershared" # Option "alwaysshared" Option "dontdisconnect" # To activate the http server Option "httpdir" "/usr/share/vnc/classes" Option "httpport" "5800" # For XEvents # The local user must accept the new connection. # An X application must be used to send the acceptance back to the server. # Using the extension library as detailed above. # Option "useraccept" # Enable the vnc service on this device, IMPORTANT!!!!!!!!!!!! Option "usevnc" # The options below are new in the 4.3.0 release # Only listen on the localhost interface # Option "localhost" # Listen on a specific interface # Option "interface" "192.168.0.1" # View only session # Option "viewonly" # The option below is new in the 4.3.0.4 release # Option "loginauth" Suggestions, Ideas etc Alan Hourihane. Email : alanh @ fairlite.demon.co.uk
|