You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
libtdevnc/vncterm
dscho ca805667e6
Build shared libraries per default
18 years ago
..
.cvsignore
ChangeLog
LinuxVNC.c do not always include rfb/keysym.h 18 years ago
Makefile.am Build shared libraries per default 18 years ago
README
TODO
VNCommand.c hide strict ansi stuff if not explicitely turned on; actually use the socklen_t test from configure.ac 20 years ago
VNConsole.c do not always include rfb/keysym.h 18 years ago
VNConsole.h global structures/functions should have "rfb", "sra" or "zrle" as prefix, 21 years ago
example.c
vga.h

README

In this stage (beta), there are two programs functional:

LinuxVNC <tty number>
	monitor a virtual console (text mode) of Linux. You need
	root privileges, or at least be in the "tty" group, because
	it reads /dev/vcsN and writes /dev/ttyN.
	It follows the same idea as WinVNC, x11vnc or OSXvnc, i.e. it
	takes an existing desktop and exports it via RFB (VNC), just that
	LinuxVNC exports text.

VNCommand <command> <args>
	executes <command> redirecting stdin from a vncviewer and stdout &
	stderr to the vnc clients. This might be renamed to vncTerm if
	there are some term capabilities added (up to now, bash doesn't look
	nice). Colours and other ANSI sequences need to be added.

My original plan was to create a program named vncTerm. It was meant to
overcome incompatibilities between different TERMs, but I found "screen" to
be just such a program. Maybe once some time in the future I'll make a
patch for screen to use VNConsole to export it's contents via RFB...

These two programs are a simple application of LibVNCServer with a small
console layer in between (VNConsole). You can use them under the terms
(not vncTerms ;-) of the GPL. They where written by Johannes E. Schindelin.