From: "Gabriel Diaz" <gabidiaz@gmail.com>
To: "Lucio De Re" <lucio@proxima.alt.za>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] can't send mail, sometimes
Date: Sat, 4 Aug 2007 11:39:11 +0200 [thread overview]
Message-ID: <82c890d00708040239h5eec3415s2d98bf2deaa45c65@mail.gmail.com> (raw)
In-Reply-To: <719c2ebf34716fbc92bb14f2afbcf00a@proxima.alt.za>
hello
then use qemu, it works on various platforms and works just like
vmware does i think :)
slds.
gabi
On 8/4/07, Lucio De Re <lucio@proxima.alt.za> wrote:
> > but taking in account all the efforts done by Ron and others on
> > supporting virtual machines, i suppose is better to use qemu, xen,
> > lguest, etc. and provide them with feedback.
>
> The philosophy here varies from the pragmatism of what works so that I
> can have what I need (VMware server works almost adequately on top of
> Ubuntu Feisty, practically out of the box) to what is good for human
> kind (Xen has lost direction and is trying to become VMware, lguest
> looks promising, specially as Rusty seems to have a direct beeline to
> Linus, but it's too closely coupled to Linux, etc., and you need an
> army of elves to track either) with numerous shades of grey in
> between.
>
> Then, there is my personal desire to, preferably, have a virtualiser
> lying below the operating system (no host "domain" - did I mention
> that I'll never get over the initial aversion to Xen that stemmed from
> needing Python to get it to work?) or, if nothing else applies, to
> make Plan 9 the host OS and, in either case, standardising on the Plan
> 9 device driver model for all Open Source operating systems.
>
> There I think Xen has a point, maybe lguest also does: Xen is
> certainly compelling all OSOS developers to relook at the platform and
> Machine Independence in a new light. For that, I believe we ought to
> thank VMware, but Xen is effectively twisting everybody's arm.
>
> Not that this subtracts anything from Ron's efforts, quite the
> contrary, but the broader the scope, the more likely we are to come up
> with a generic solution. One that resembles what IBM did right more
> than thirty years ago.
>
> ++L
>
>
next prev parent reply other threads:[~2007-08-04 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 3:58 john
2007-08-03 10:04 ` Gabriel Diaz
2007-08-03 4:09 ` john
2007-08-03 10:24 ` Gabriel Diaz
2007-08-03 4:41 ` john
2007-08-03 10:38 ` Lucio De Re
2007-08-03 10:36 ` Lucio De Re
2007-08-03 11:14 ` Gabriel Diaz
2007-08-04 9:07 ` Lucio De Re
2007-08-04 9:39 ` Gabriel Diaz [this message]
2007-08-04 10:00 ` Lucio De Re
2007-08-04 4:06 ` john
2007-08-04 10:13 ` Lucio De Re
2007-08-04 4:21 ` john
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=82c890d00708040239h5eec3415s2d98bf2deaa45c65@mail.gmail.com \
--to=gabidiaz@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=lucio@proxima.alt.za \
/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).