From: Andrey A Mirtchovski <aam396@mail.usask.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] X on Plan 9
Date: Wed, 18 Apr 2001 18:15:53 -0600 [thread overview]
Message-ID: <Pine.GSO.4.10.10104181815450.738-100000@ultra5c.usask.ca> (raw)
In-Reply-To: <Pine.GSO.4.10.10104181708050.738-100000@ultra5c.usask.ca>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1647 bytes --]
damit :)
On Wed, 18 Apr 2001, Andrey A Mirtchovski wrote:
> hi,
>
> i'm not posting this to the list, since i'm not sure how many people need to
> know about this, but something called x.tar.gz (or a variation thereof) was
> located on the plan9.bell-labs.com ftp site at least in january this year..
> i think it was the infamous X port..
>
> i don't remember the exact location, though... i remember downloading and
> unzipping it, but that was all..
>
> hope this helps in any way :)
>
> On Wed, 18 Apr 2001 anothy@cosym.net wrote:
>
> > the APE paper (i think) mentions that APE has been used to
> > build X11 on Plan 9, but that it's not included in the
> > distribution because it's too much work to maintain. i
> > imagine the presence of the very good vnc client also helps
> > negate the need for X for most people.
> >
> > however, shame me as it does to admit it, i'd still find a
> > local X server very useful. there are about a half-dozen X
> > programs i find useful, and i'm not up to porting them all
> > the Plan 9's /dev/draw.
> >
> > so... understanding that it's totally unsupported... can
> > whoever did the work in the Labs either share whatever
> > changes were made? i assume that, at least, X had to be told
> > how to talk to /dev/draw. i suspect various things also
> > needed to be done to convince it to 'configure' properly.
> >
> > if nobody has any info, i'm going to give it a shot myself,
> > but X is an intimidating (read: freakin' huge!) body of
> > crap^Wcode, and i'd rather not duplicate work someone else's
> > already done.
> > -α.
> >
>
>
next prev parent reply other threads:[~2001-04-19 0:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 22:56 anothy
2001-04-18 23:12 ` Andrey A Mirtchovski
2001-04-19 0:15 ` Andrey A Mirtchovski [this message]
2001-04-18 23:41 ` Alexander Viro
2001-04-24 9:00 ` bob
2001-04-18 23:50 Russ Cox
2001-04-19 0:11 ` Alexander Viro
2001-04-19 0:14 ` Boyd Roberts
2001-04-19 3:03 anothy
2001-04-19 4:00 okamoto
2001-04-23 9:54 ` David Rubin
2001-04-23 11:10 ` Boyd Roberts
2001-04-19 7:41 forsyth
2001-04-19 19:03 anothy
2001-04-19 21:27 ` Boyd Roberts
2001-04-19 22:26 ` Ronald G Minnich
2001-04-23 9:55 ` Douglas A. Gwyn
2001-04-23 11:12 ` Boyd Roberts
2001-04-19 19:33 forsyth
2001-04-19 21:58 anothy
2001-04-19 22:14 ` Scott Schwartz
2001-04-19 22:32 ` Boyd Roberts
2001-04-19 22:35 ` Boyd Roberts
2001-04-19 23:06 ` Dan Cross
2001-04-23 9:55 ` David Rubin
2001-04-23 10:19 ` Boyd Roberts
2001-04-20 0:56 okamoto
2001-04-20 3:02 Russ Cox
2001-04-20 3:32 anothy
2001-04-20 3:39 anothy
2001-04-20 6:59 nemo
2001-04-20 8:04 forsyth
2001-04-21 7:48 geoff.9fans
2001-04-23 11:20 forsyth
2001-04-24 15:02 ` David Rubin
2001-04-25 2:17 ` Boyd Roberts
2001-04-25 2:04 okamoto
2001-04-25 2:49 ` Scott Schwartz
2001-04-26 16:40 ` Douglas A. Gwyn
2001-04-25 10:41 rob pike
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=Pine.GSO.4.10.10104181815450.738-100000@ultra5c.usask.ca \
--to=aam396@mail.usask.ca \
--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).