From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Again: (self)hosted Plan9? Was: [9fans] extending xen to allow
Date: Tue, 12 Dec 2006 16:13:42 -0700 [thread overview]
Message-ID: <13426df10612121513l5ce5490fkcabf1876cbe56317@mail.gmail.com> (raw)
In-Reply-To: <762F6304-7D8B-4BA9-B78F-32E286A6D433@lanl.gov>
On 12/12/06, Latchesar Ionkov <lionkov@lanl.gov> wrote:
> This may solve the no-firefox-and-mplayer-for-plan9 problem, but I
> don't see how it solves the no-plan9-drivers-for-my-laptop one.
Hence the approach we are taking with xen. You get a linux, you get a
Plan 9, you get holes torn in the I/O and memory spaces from Plan 9 to
hardware to let you doink hardware and write drivers under Plan 9,
and, with any luck, crash the machine at will.
I think it's going to work out. At least the crashing part.
Aki is already regularly crashing linux from user mode, so how hard can it be?
ron
p.s. with the new web 2.0 in my firefox browser, with 64M resident out
of 136M, I am seeing that the mouse "sticks" and as I move the mouse
random shit gets highlighted and erased. Fun.
next prev parent reply other threads:[~2006-12-12 23:13 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 23:52 erik quanstrom
2006-12-12 0:22 ` Dave Eckhardt
2006-12-12 2:29 ` Russ Cox
2006-12-12 5:01 ` Lucio De Re
2006-12-12 14:21 ` Brantley Coile
2006-12-12 9:22 ` Charles Forsyth
2006-12-12 9:41 ` Bruce Ellis
2006-12-12 14:31 ` Brantley Coile
2006-12-12 14:55 ` ron minnich
2006-12-12 15:18 ` Eric Van Hensbergen
2006-12-12 15:25 ` erik quanstrom
2006-12-12 22:01 ` ron minnich
2006-12-12 22:19 ` Latchesar Ionkov
2006-12-12 23:13 ` ron minnich [this message]
2006-12-12 23:47 ` Bakul Shah
2006-12-12 23:37 ` Charles Forsyth
2006-12-13 18:27 ` ron minnich
2006-12-13 19:02 ` Matt
2006-12-13 19:13 ` Latchesar Ionkov
2006-12-14 18:55 ` David Leimbach
2006-12-13 0:41 ` quite Off Topic: " Georg Lehner
2006-12-13 3:46 ` Jack Johnson
2006-12-13 21:04 ` ron minnich
2006-12-13 21:13 ` Russ Cox
2006-12-13 21:30 ` Bakul Shah
2006-12-12 9:41 ` Gabriel Diaz
2006-12-12 9:51 ` Bruce Ellis
2006-12-12 10:28 ` Lucio De Re
2006-12-12 10:30 ` Bruce Ellis
2006-12-12 23:26 ` Scott Schwartz
2006-12-12 14:42 ` Brantley Coile
2006-12-12 14:51 ` Gabriel Diaz
2006-12-12 11:49 ` Charles Forsyth
2006-12-12 14:17 ` Brantley Coile
2006-12-13 0:37 ` David Leimbach
2006-12-13 1:51 ` Aki Nyrhinen
-- strict thread matches above, loose matches on Subject: below --
2006-12-10 20:19 erik quanstrom
2006-12-10 13:00 erik quanstrom
2006-12-07 5:01 Again: (self)hosted Plan9? Was: [9fans] extending xen to allow driver ron minnich
2006-12-07 5:46 ` Again: (self)hosted Plan9? Was: [9fans] extending xen to allow Lucio De Re
2006-12-07 6:06 ` ron minnich
2006-12-09 4:21 ` Chad Dougherty
2006-12-09 11:21 ` Steve Simon
2006-12-09 12:43 ` Lucio De Re
2006-12-09 12:56 ` erik quanstrom
2006-12-10 4:55 ` geoff
2006-12-10 5:04 ` andrey mirtchovski
2006-12-10 20:16 ` Charles Forsyth
2006-12-10 20:56 ` Francisco J Ballesteros
2006-12-10 21:38 ` Charles Forsyth
2006-12-10 20:52 ` ron minnich
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=13426df10612121513l5ce5490fkcabf1876cbe56317@mail.gmail.com \
--to=rminnich@gmail.com \
--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).