From: Christoph Hellwig <hch@infradead.org>
To: Ben Pfaff <blp@cs.stanford.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Cooperative Linux
Date: Mon, 26 Jan 2004 19:44:08 +0000 [thread overview]
Message-ID: <20040126194408.A3450@infradead.org> (raw)
In-Reply-To: <8765ey3as9.fsf@pfaff.stanford.edu>; from blp@cs.stanford.edu on Mon, Jan 26, 2004 at 09:00:22AM -0800
On Mon, Jan 26, 2004 at 09:00:22AM -0800, Ben Pfaff wrote:
> > On Sun, Jan 25, 2004 at 08:59:52PM -0800, Ben Pfaff wrote:
> >> For what it's worth, this has been done in the proprietary world
> >> as successful commercial software, as VMware ESX Server.
> >
> > Which seems to be nothing more than a hacked up Linux..
>
> Not even close to true. ESX Server includes a hacked up Linux as
> part of its front end, but there's a lot more than that.
Well, I've only seen their driver API is the linux API with slight changes.
Can you elaborate what "includes a hacked up Linux as part of its front end"
means and where we can get the source to the rest of this frontend (and
the linux changes)?
next prev parent reply other threads:[~2004-01-26 19:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 19:35 [ANNOUNCE] Cooperative Linux Dan Aloni
2004-01-25 20:01 ` Karim Yaghmour
2004-01-26 3:40 ` Nuno Silva
2004-01-26 3:57 ` JustFillBug
2004-01-26 4:59 ` Ben Pfaff
2004-01-26 9:19 ` Christoph Hellwig
2004-01-26 17:00 ` Ben Pfaff
2004-01-26 19:44 ` Christoph Hellwig [this message]
2004-01-26 20:04 ` Omkhar Arasaratnam
2004-01-26 5:04 ` Karim Yaghmour
2004-01-26 5:06 ` Nuno Silva
2004-01-26 6:36 ` Karim Yaghmour
2004-01-26 11:35 ` Rik van Riel
2004-01-26 15:20 ` Karim Yaghmour
2004-01-26 11:32 ` Rik van Riel
2004-01-27 0:20 ` David Schwartz
2004-01-26 4:26 ` Dan Aloni
2004-01-26 5:01 ` Karim Yaghmour
2004-01-26 7:23 ` Dan Aloni
-- strict thread matches above, loose matches on Subject: below --
2004-01-29 5:57 Paul Zimmerman
2004-01-29 9:10 ` Dan Aloni
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=20040126194408.A3450@infradead.org \
--to=hch@infradead.org \
--cc=blp@cs.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
/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