On Feb 3, 2008 12:49 PM, Ilya Konstantinov <[EMAIL PROTECTED]> wrote:
> On Feb 3, 2008 11:15 AM, Shachar Shemesh <[EMAIL PROTECTED]> wrote: > > > VNC on Windows behaves differently than on Linux. On Linux, it opens its > > own unique X server, and then exports its display using the VNC > > protocol. On Windows, VNC server exports the main Windows display. > > > Nowadays, you have VNC servers which act as X11 clients and export > whatever X11 display you point them at. Those are the VNC servers which come > with GNOME and KDE as their "remote desktop" offerings. > > Here's one: > http://www.karlrunge.com/x11vnc/ > > BTW, those kind of VNC servers only became possible (with reasonable > performance) with the introduction of the DAMAGE extension, so they pretty > much have to run on a modern X server - or otherwise there'll be very > CPU-intensive screen polling. > This describes a configuration more like Xvnc: http://www.karlrunge.com/x11vnc/#faq-xvfb See also the discussion there about using x11vnc from inetd for spawning new X sessions on demand in response to VNC connections.
