From: Patrick Kelly <kameo76890@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] remote access to audio devices
Date: Tue, 1 Dec 2009 19:26:24 -0500 [thread overview]
Message-ID: <285891FC-C2F9-492D-9263-582389917D29@gmail.com> (raw)
In-Reply-To: <C8EA3DA7-DD78-45DC-91EA-35643229AC35@fastmail.fm>
On Dec 1, 2009, at 17:28, Ethan Grammatikidis <eekee57@fastmail.fm>
wrote:
>
> On 1 Dec 2009, at 8:44 pm, Steve Simon wrote:
>
>>> VNC can (has been) be a butt-saver' - but pales in comparison to
>>> remote desktop
>>> / remote X for relative responsiveness and seamlessness.
>>
>> My experience of serving a Windows desktop to a plan9 terminal
>> is that TightVNC with the DFMirage "Mirror driver" works really well.
>
> I've had responsiveness issues when the viewing machine hasn't
> enough CPU power to decode the screen data in real-time. A lot of
> power seems to be needed, my PDA, a 416MHz ARM can't cope with any
> compression at all, I have to limit vncviewer to copyrect and raw
> encodings only. Encoding doesn't seem to need half as much CPU
> power. I ran Xvnc on a headless server with a 400MHz AMD K6 with no
> issues that I recall.
Now I don't have any expertise with VNC, but decoding anything, is
supposed to take less time than encoding it. I would check into that.
>
> All that gear was using either TightVNC or the plain vnc-
> x.y.z.tar.gz from RealVNC. When using Vine Server on a 466MHz Apple
> screen updates are not really adequate, while the mouse pointer
> lags if I use the VNC server supplied with OS X Tiger on the same
> machine. x0vncserver is a known problem server which I haven't used,
> IIRC it basically works by taking screenshots continuously and
> sending those.
>
next prev parent reply other threads:[~2009-12-02 0:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<3aaafc130911242005m5cfc0d8bs92094b33757711d9@mail.gmail.com>
2009-11-25 4:08 ` [9fans] Scanners erik quanstrom
2009-11-25 9:45 ` Peter A. Cejchan
2009-11-25 11:32 ` Andreas Zell
2009-11-25 12:20 ` Peter A. Cejchan
2009-11-25 12:26 ` Peter A. Cejchan
2009-11-25 14:34 ` hiro
2009-11-25 14:28 ` Andreas Zell
2009-11-25 14:33 ` Jorden Mauro
2009-11-25 14:44 ` hiro
2009-11-25 16:45 ` Peter A. Cejchan
2009-11-25 16:43 ` Peter A. Cejchan
2009-11-25 17:03 ` Jack Norton
2009-11-26 0:51 ` cinap_lenrek
2009-11-25 16:53 ` ron minnich
2009-11-25 17:04 ` Brian L. Stuart
2009-11-25 17:08 ` John Floren
2009-11-25 19:04 ` Brian L. Stuart
2009-12-01 19:52 ` Steve Simon
2009-11-25 17:12 ` hiro
2009-11-25 17:20 ` erik quanstrom
2009-11-25 17:47 ` Anthony Sorace
2009-11-25 17:51 ` erik quanstrom
2009-11-26 3:48 ` Anthony Sorace
2009-11-26 5:16 ` W B Hacker
2009-11-25 19:18 ` ron minnich
2009-11-25 19:49 ` W B Hacker
2009-11-26 0:07 ` Charles Forsyth
2009-11-26 4:55 ` W B Hacker
2009-11-26 6:39 ` [9fans] remote access to audio devices Sam Watkins
2009-11-26 8:59 ` W B Hacker
2009-12-01 20:44 ` Steve Simon
2009-12-01 22:28 ` Ethan Grammatikidis
2009-12-02 0:26 ` Patrick Kelly [this message]
2009-12-02 3:00 ` Sam Watkins
2009-12-25 9:50 ` Ethan Grammatikidis
2009-11-26 13:03 ` [9fans] Scanners Ethan Grammatikidis
2009-11-26 20:23 ` [9fans] 9p resource sharing [was: Scanners] Tim Newsham
2009-11-26 20:33 ` Tim Newsham
2009-11-26 23:39 ` Enrico Weigelt
2009-11-27 4:36 ` Tim Newsham
2009-11-27 5:30 ` Enrico Weigelt
2009-11-26 22:59 ` [9fans] Scanners Enrico Weigelt
2009-11-25 14:17 ` Jorden Mauro
[not found] <<F7BCB408-74FB-4E3C-BBAF-C52E0C2A15B3@fastmail.fm>
2009-12-25 9:57 ` [9fans] remote access to audio devices erik quanstrom
2009-12-25 14:49 ` Jorden Mauro
2010-01-05 12:10 ` Enrico Weigelt
2009-12-26 3:39 ` Anthony Sorace
2009-12-27 10:07 ` Ethan Grammatikidis
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=285891FC-C2F9-492D-9263-582389917D29@gmail.com \
--to=kameo76890@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).