On Sun, 2006-09-03 at 06:26, Robin Hill wrote: > On Sun Sep 03, 2006 at 03:06:06AM -0400, Calvin Webster wrote: > > > =================[Any 2.6 Linux Kernels?]================= > > I'm curious why even development versions of TightVNC are being built > > for an already obsolete distribution? Are there problems building or > > running on the 2.6 kernels? More importantly, are there any issues > > running TightVNC with the latest open source X servers (RHEL 4 uses > > xorg-x11-6.8.2-1.EL.13.37)? > > > I'm not sure why the kernel version would affect things at all, but I > can confirm that TightVNC works perfectly well on 2.6 kernels. It also > works with xorg (either as provided or rebuilt against xorg). SuSE > include tightvnc as standard with their distributions, so you may want > to check whether they include any additional patches, etc.
I'm glad to hear that. Thank you Robin. > > ===============[Native and Virtual Displays]=============== > > 1. I don't see any "vnc.so" module in the tightvnc-server RPM. Does > > TighVNC not support remote native X display? In other words, can I > > connect to display :0 on a server and control the local console > > remotely? > > > I can't say whether this is included in the RPM, but it is certainly > available for TightVNC. I suspect there may be a separate RPM > containing this, as most users need only one or the other. David Troesch, from the TightVNC list, seems to think that it's there, but I haven't found it. > > 2. Am I likely to have problems with my multiple vnc services if I > > switch to TightVNC? I'm using XDM (GDM) for these. Here is an excerpt > > representing one of the high-resolution virtual displays from my RHEL 4 > > /etc/xinetd.d/vnc file (watch for line-wrap in your message). > > > You may have issues here as TightVNC doesn't look to support all of > these options - I think several of these are RealVNC v4.x additions. I guess I'll play around with it on one of my test VM's as time permits. > > ===============[RealVNC -> TightVNC Versions]=============== > > The main TightVNC home page says the it is "derived from the popular VNC > > software. Is this a forked development effort or does it track directly > > with RealVNC releases? > > > It was forked from the RealVNC v3 code base - I've no idea whether they > plan a resync with the v4.x release at some point or not, though it's > taken a couple of years for the latest version to reach release > candidate status so I wouldn't get your hopes up. David believes that VNC 4.x was integrated into the code base a few months ago. Apparently, maintainers pull VNC source into their code base at arbitrary intervals, as their workload permits, but make no announcements about it on their web site. _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
