public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Toby 'qubit' Cubitt" <tsc25@cantab.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Modular X
Date: Sun, 2 Apr 2006 18:19:58 +0200	[thread overview]
Message-ID: <20060402161958.GA17443@mpq3p6.mpq.mpg.de> (raw)
In-Reply-To: <200604021626.05956.Rick.van.Hattem@fawo.nl>

On Sun, Apr 02, 2006 at 04:26:00PM +0200, Rick van Hattem wrote:
> On Saturday 01 April 2006 23:47, Jim wrote:
> > On Sat, 2006-04-01 at 22:29 +0200, Alexander Skwar wrote:
> > > alexander@blatt /var/db/pkg $ epm -qf `which xmkmf `
> > > imake-1.0.1-r1
> > >
> > > Please file a bug against tightvnc, as it's missing
> > > a dependency.
> >
> > Will do.
> >
> > > BTW: Why use tightvnc at all? Realvnc 4 is as fast in
> > > my experience and there's still somebody workign on it -
> > > seeing that the last update to tightvnc is dated
> > > July 2005, I doubt that anybody maintains it anymore.
> >
> > I am testing out the different vnc versions along with freeNX to see
> > what will give me the fastest remote desktop.
> >
> > > Alexander Skwar
> >
> > Jim
> When you're done testing please report/publish the results, I'm also very 
> interested in a fast remote desktop system.
> 
> Tightvnc can hog the cpu with the compression sometimes so that's not always a 
> good solution either.

I've tried tightVNC and freeNX, both over a relatively slow DSL link
and on an old pentium2 450, and whilst both were usable there's no
competition: freeNX wins hands down.

I also like the fact that freeNX also lets you run single remote
applications, instead of always having to start up a complete remote
desktop - much closer to normal X-forwarding.

The only downside to freeNX was it was more complicated to get
working. (But that may have been due to the complicated things I was
trying to do: everything had to be tunnelled through a firewall using
ssh port-forwarding, and I needed to get my X server to talk to a
remote font server, also via ssh tunnelling, so that fonts on the
application I was running over freeNX would work.)

HTH,

Toby
-- 
PhD Student
Quantum Information Theory group
Max Planck Institute for Quantum Optics
Garching, Germany

email: toby@dr-qubit.org
web: www.dr-qubit.org
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-04-02 16:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-01 20:12 [gentoo-user] Modular X Jim
2006-04-01 20:29 ` Alexander Skwar
2006-04-01 20:58   ` Rick van Hattem
2006-04-01 21:47   ` Jim
2006-04-02  9:06     ` W.Kenworthy
2006-04-02 14:26     ` Rick van Hattem
2006-04-02 16:19       ` Toby 'qubit' Cubitt [this message]
2006-04-03  6:23         ` Alexander Skwar
2006-04-03 15:35           ` Toby 'qubit' Cubitt
2006-04-03 21:02             ` Alexander Skwar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060402161958.GA17443@mpq3p6.mpq.mpg.de \
    --to=tsc25@cantab.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox