From: George Michaelson <ggm@apnic.net>
To: 9fans@cse.psu.edu
Cc: rminnich@lanl.gov
Subject: Re: [9fans] xen port?
Date: Sun, 21 Mar 2004 17:24:43 +1000 [thread overview]
Message-ID: <20040321172443.076993e8@dhcppc1> (raw)
In-Reply-To: <Pine.LNX.4.44.0403190752090.13503-100000@maxroach.lanl.gov>
On Fri, 19 Mar 2004 07:52:30 -0700 (MST) ron minnich <rminnich@lanl.gov> wrote:
>On Fri, 19 Mar 2004, Leo Caves wrote:
>
>> I am interested to hear opinion on what xen might offer in the Plan
>> 9/inferno world-view.
>
>my one interest was that I could run auth, fs, and term on one laptop.
>
>ron
Me three. and, get around non-supported h/w by using a virtual machine instance
which would be a longterm port available across changing pee cee hardware.
xens website claims to reveal a lot of the underlying machine speed-wise.
It may depend what you compare it to.
-George
next prev parent reply other threads:[~2004-03-21 7:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 23:10 George Michaelson
2004-03-19 14:01 ` Leo Caves
2004-03-19 14:52 ` ron minnich
2004-03-20 4:36 ` Martin C.Atkins
2004-03-20 5:24 ` andrey mirtchovski
2004-03-20 14:34 ` ron minnich
2004-03-21 7:24 ` George Michaelson [this message]
2004-03-21 14:03 ` Russ Cox
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=20040321172443.076993e8@dhcppc1 \
--to=ggm@apnic.net \
--cc=9fans@cse.psu.edu \
--cc=rminnich@lanl.gov \
/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).