diff options
author | Matteo Bernardini <ponce@slackbuilds.org> | 2021-04-17 09:58:11 +0200 |
---|---|---|
committer | Robby Workman <rworkman@slackbuilds.org> | 2021-04-18 00:01:08 -0500 |
commit | 8b8cd0236124621ee8b9935a9304a59892883804 (patch) | |
tree | 1c4c2daed2927d4e9a4109c81c69f5bf2520e66d /network/tightvnc/README | |
parent | 56187fff16f0beef71e458a06e8be753a4745aeb (diff) |
network/tightvnc: Removed (linux development abandoned).
a viable alternative is its fork tigervnc in /extra
Signed-off-by: Matteo Bernardini <ponce@slackbuilds.org>
Diffstat (limited to 'network/tightvnc/README')
-rw-r--r-- | network/tightvnc/README | 29 |
1 files changed, 0 insertions, 29 deletions
diff --git a/network/tightvnc/README b/network/tightvnc/README deleted file mode 100644 index 6c055516e3496..0000000000000 --- a/network/tightvnc/README +++ /dev/null @@ -1,29 +0,0 @@ -tightvnc (VNC viewing application) - -TightVNC is a free remote control software package. With TightVNC, you can -see the desktop of a remote machine and control it with your local mouse and -keyboard, just like you would do it sitting in the front of that computer. - -TightVNC is: - -* free for both personal and commercial usage, with full source code available -* useful in administration, tech support, education, and many other purposes -* cross-platform, available for Windows and Unix, with Java client included -* compatible with standard VNC software, conforming to RFB protocol specs - -TightVNC also ships with Xvnc, a headless X server that speaks the VNC -protocol. - -NOTE: vncserver/Xvnc requires a configuration file (tightvncserver.conf) in -/etc to operate. A suitable, basic, configuration file is by this slackbuild -in /usr/doc/tightvnc-1.3.10. Copy this file to /etc before attempting to -launch vncserver/Xvnc. - -Also included is a small, optional, patch to vncserver (vncserver.patch), -contributed by Andrei Descuĺ–¢, which modifies the vncserver startup to use -the system configured xinitrc instead of the minimal xterm/twm configuration -used by default. Note that if you have launched vncserver prior to applying -the optional patch, you will need to remove the $HOME/.vnc/xstartup file to -use the alternate configuration. If you wish to use the optional patch, you -will need to apply it manually (i.e., using the 'patch' command from the -command line). |