From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] no job control; thank you!
Date: Thu, 18 Jul 2002 18:34:22 +0200 [thread overview]
Message-ID: <20020718183421.T14964@cackle.proxima.alt.za> (raw)
In-Reply-To: <00cd01c22e76$da078620$6501a8c0@KIKE>; from matt on Thu, Jul 18, 2002 at 05:19:09PM +0100
On Thu, Jul 18, 2002 at 05:19:09PM +0100, matt wrote:
>
> I was thinking that this would make a very useful addition to plan9. By
> opting for vnc-vga one can avoid vga hell to get an auth/cpu server up and
> running. One of the set-up problems is that you might need two computers so
> that you can edit plan9.ini or edit/compile the $vga_driver.c
>
Yes, that's certainly an interesting and intriguing option. I
haven't really looked at vncs yet, but the possibility ought to
exist...
> I was thinking that a pseudo VGA driver would pretend that there was VGA
> hardware running and running vncs would expose it.
>
A VMware-like VGA device, hiding behind the framebuffer, hiding
behind the VNC protocol. Where do we sneak in the fileserver?
> Downside is the lack of authentication possible if one continued to use the
> system in such a state but at least you would / could be using it.
>
Authentication can be promoted to factotum, I'm sure; if memory
serves, the VNC protocol is extensible. It would be nice to be
able to pick your session by user id, if the system is willing to
collaborate.
++L
next prev parent reply other threads:[~2002-07-18 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 15:02 rog
2002-07-18 14:13 ` Sam
2002-07-18 16:19 ` matt
2002-07-18 16:34 ` Lucio De Re [this message]
2002-07-18 21:37 ` Chris Hollis-Locke
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 16:18 David Gordon Hogan
2002-07-30 5:11 Russ Cox
2002-07-18 14:53 forsyth
2002-07-18 3:49 rob pike, esq.
2002-07-18 14:21 ` Douglas A. Gwyn
2002-07-18 3:23 Geoff Collyer
2002-07-18 18:30 ` Chet Ramey
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=20020718183421.T14964@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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).