Re: remote X vs VNC

From: Michael Schnell (mschnell_at_lumino.de)
Date: 07/16/03


Date: Wed, 16 Jul 2003 14:17:51 +0200


> Its main
> drawback is that the VNC X Server actually runs on the Linux side and
> takes up memory there.

So not a good idea for remote controlling an embedded device.

> Unfortunately, the X protocol cannot easily be
> squeezed through SSH, at least not completely without a kludge.

But it should pass a VPN if security is needed.

-Michael



Relevant Pages

  • Re: Program is "stopped" when sent to background
    ... When I first set up the Linux box, I had to connect it to the ... I don't know about vnc. ... you can generate a linux kernel that redirects the system console to the ... When I designed and ran server farms for industry ...
    (comp.os.linux)
  • Re: How hard is socket programming?
    ... As far as I can tell FastCGI is good here too. ... Again, you are not a server expert, so you ... memory usage to no more than 75% of available RAM in ... Linux probably does ...
    (microsoft.public.vc.mfc)
  • Re: VNC into Linux server
    ... > the RealVNC server). ... > on the Linux box from the Win2K box running the TightVNC viewer. ... > It appears the Linux box is listening on port 5901. ... The VNC viewer ...
    (comp.os.linux.networking)
  • Re: Sweet Success
    ... > Let me say upfront that I like Linux in general, and RedHat in particular. ... a server again in the next month. ... can VNC to each of the client workstations if the need arises; ...
    (RedHat)
  • Re: How hard is socket programming?
    ... As far as I can tell FastCGI is good here too. ... Again, you are not a server expert, so you ... Linux probably does ... it has no need for additional memory would be an idiotic ...
    (microsoft.public.vc.mfc)