From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] xen bit-rot
Date: Wed, 16 May 2007 20:35:09 +0200 [thread overview]
Message-ID: <8c35b2735d810496c0b5431baf347d91@proxima.alt.za> (raw)
In-Reply-To: <40fd39edd6b554aff3984e71f56381b8@hamnavoe.com>
> I've brought it up to date again, and also removed the
> "restart='never'" line from the example Plan 9 domain config files,
> because the 3.0.4 xen daemon seems to object to it.
Who said Plan 9 is dying?
Actually, my suggestion to Ron Minnich was to reverse the tables on
Xen by putting Plan 9 in Dom 0 and offering Plan 9-like device drivers
via Xen to paravirtualized kernels so that all Open Source kernels
would have a sensible basis to work from.
Redirecting all device driver development towards the Plan 9 model
ought to make a huge, positive difference to the end result.
++L
next prev parent reply other threads:[~2007-05-16 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 18:28 Richard Miller
2007-05-16 18:35 ` lucio [this message]
2007-05-16 18:55 ` ron minnich
2007-05-16 19:06 ` lucio
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=8c35b2735d810496c0b5431baf347d91@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).