From: Digby Tarvin digbyt@acm.org
Subject: [9fans] X device
Date: Tue, 25 Aug 1998 15:24:45 +0100 [thread overview]
Message-ID: <19980825142445.Pf8FU5Zga2FBZURVrYz2wKA7jSPNHhfxsgvM3vzuVlU@z> (raw)
This is somthing I suggested in a private mail, which I thought
I would put to the list to see if any more experienced Plan9'ers
could see any problems with my proposal.
What I would like is a Plan9 display driver that, instead of
talking to a display adapter card on the bus, controls a remote
display using the network and the X protocol.
Effectively, I want to be able to use my X terminal as a Plan9
console. This would be different from implementing Xlib
on Plan9, because that would result in a situation where only
X aware applications could be used on X-terminals.
If the X terminal looked like a Plan9 device, then all existing
applications should work unmodified, and a single Plan9 system
would become multi-user in (the Unix sense, rather than the
Windows NT sense of one screen per CPU).
Also, if the driver were to talk to a window on the X terminal
(which could be the root window), then it would be possible
to use the same X term to access other operating systems
at the same time.
Does anyone know if there is any fundamental conflict between the
types of access a Plan9 screen driver needs to make, and the
capabilities of the X protocol?
The other possibility that came to mind was implementing a
VNC server for Plan9. That would allow users of Unix/Doze/NT/Mac
to pull up a Plan9 system on their screens without having to
have a copy of the OS to run..
Regards,
DigbyT
--
Digby R. S. Tarvin digbyt@acm.org
http://www.cthulhu.dircon.co.uk
next reply other threads:[~1998-08-25 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-25 14:24 Digby [this message]
1998-08-25 16:13 rob
1998-08-25 17:03 Digby
1998-08-25 17:48 rob
1998-08-25 18:56 Digby
1998-08-25 19:30 Scott
1998-08-26 8:18 Elliott.Hughes
1998-08-26 8:59 forsyth
1998-08-26 17:49 Russ
1998-09-06 16:50 miller
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=19980825142445.Pf8FU5Zga2FBZURVrYz2wKA7jSPNHhfxsgvM3vzuVlU@z \
--to=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).