From: "Curt Micol" <asenchi@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Xen Installation
Date: Mon, 19 May 2008 23:56:26 -0400 [thread overview]
Message-ID: <8d9c091a0805192056q2df11104k133c084c6ed00a2e@mail.gmail.com> (raw)
In-Reply-To: <13426df10805192022x7621438yc96f6b81b65a5e99@mail.gmail.com>
On Mon, May 19, 2008 at 11:22 PM, ron minnich <rminnich@gmail.com> wrote:
> here's the best help I can give: don't use xen.
[snip]
> p.s. I wrote the first Xen port. If Xen had not turned bad, I would
> not be giving you this advice.
Hey ron,
Could you explain what 'turned bad' and why you no longer prefer xen?
This is just for my own curiosity, I'd like to hear your opinion.
I'll also begin looking through the archives to see if I missed
something there.
Thanks,
--
# Curt Micol
next prev parent reply other threads:[~2008-05-20 3:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 2:01 Jonny Morrill
2008-05-20 3:22 ` ron minnich
2008-05-20 3:56 ` Curt Micol [this message]
2008-05-20 4:22 ` ron minnich
2008-05-20 6:07 ` Stefan Hajnoczi
2008-05-21 0:44 Jonny Morrill
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=8d9c091a0805192056q2df11104k133c084c6ed00a2e@mail.gmail.com \
--to=asenchi@gmail.com \
--cc=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).