From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] paper ``Rio, the Plan 9 Window System''
Date: Fri, 9 Aug 2002 15:19:19 +0900 [thread overview]
Message-ID: <720e924c84f37c7674cf41f2e32ccf6d@granite.cias.osakafu-u.ac.jp> (raw)
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
If Rob won't write User's manual of rio, fs etc, why someone in Vitanuova
can write one, and sell the books of manuals with it. I say this, because
Plan 9 has two aspects to be considered, one is a target for OS reseachers,
and the other is a clearer base for someone, probably concerning with
education? to use it for applications. Vitanuova, probably, targetting the latter,
I suppose.
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 3903 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 219 bytes --]
it might be worth noting that another paper, ``A Concurrent Window System'',
is helpful in understanding the underlying model and to a useful extent the
internal structure of rio and its use of Channels (thread(2)).
[-- Attachment #2.1.2: Type: message/rfc822, Size: 1764 bytes --]
From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] paper ``Rio, the Plan 9 Window System''
Date: Thu, 8 Aug 2002 08:49:50 -0400
Message-ID: <912418b08142b7626f8a45c18bb299ae@plan9.bell-labs.com>
Rio never seemed enough of an advance to be worth a paper.
The 8 paper describes the most important property, providing
a window system as a file server.
The only novel feature of rio is the way it avoids multiplexing
the graphics device, letting the driver do that job. (8 muxed
all graphics ops itself.) But other window managers can do that,
so it's not worth a paper either.
-rob
next reply other threads:[~2002-08-09 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 6:19 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 18:44 Andrey S. Kukhar
2002-08-08 13:04 C H Forsyth
2002-08-08 12:49 rob pike, esq.
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=720e924c84f37c7674cf41f2e32ccf6d@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).