From: Scott Schwartz schwartz@finch.cse.psu.edu
Subject: [9fans] Plan9 commercial licenses
Date: Tue, 30 Sep 1997 15:11:21 -0400 [thread overview]
Message-ID: <19970930191121.L9kWYJqezWGzud9bbMP8rxB5lj9MQ467KP86novXEMU@z> (raw)
eld@jewel.ucsd.edu (Eric Dorman) writes:
| Of course, might be slicker to have bitblt code in a userprocess,
| but would there a performance hit? Might not matter that much.
QNX does that, and apparently works well. Microkernel, anyone?
next reply other threads:[~1997-09-30 19:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-30 19:11 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-01 7:45 elliott
1997-09-30 21:45 Eric
1997-09-30 21:19 jmk
1997-09-30 21:07 Eric
1997-09-30 20:02 Eric
1997-09-30 19:56 jmk
1997-09-30 19:09 David
1997-09-30 18:44 Eric
1997-09-30 18:20 Scott
1997-09-30 16:41 Eric
1997-09-30 16:23 Frank
1997-09-30 15:14 G.David
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=19970930191121.L9kWYJqezWGzud9bbMP8rxB5lj9MQ467KP86novXEMU@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).