From: Karim Yaghmour <karim@opersys.com>
To: Dan Aloni <da-x@gmx.net>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Cooperative Linux
Date: Sun, 25 Jan 2004 15:01:34 -0500 [thread overview]
Message-ID: <4014209E.2040908@opersys.com> (raw)
In-Reply-To: <20040125193518.GA32013@callisto.yi.org>
Dan Aloni wrote:
> The bottom line is that it allows us to run Linux on an unmodified
> Windows 2000/XP system in a practical way (the user just launches
> an app), and it may eventually bring Linux to a large sector of desktop
> computer users who wouldn't even care about trying to install a
> dual boot system or boot a Linux live CD (like Knoppix).
>
> Screen-shots and further details at:
>
> http://www.colinux.org
Cool!
> Our motto is:
>
> "If Linux runs on every architecture, why should another
> operating system be in its way?"
Indeed.
> coLinux is similar to plex86 in a way that it implements a Linux-specific
> lightweight VM with I/O virtualization. However, it is designed to be
> mostly host-OS independent, so that with minimal porting efforts it
> would be possible to run it under Solaris, Linux itself, or any operating
> system that supports loading kernel drivers, under any architecture that
> uses an MMU. Unlike other virtualization methods, it doesn't base its
> implementation on exceptions that are caused by instructions.
Right, that's the way to go with an OS for which the source is available.
Have you looked at the work that's been going on with the Adeos nanokernel:
http://www.opersys.com/adeos/index.html
Some of the infrastructure required by all these virtualization solutions
is fairly similar.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next prev parent reply other threads:[~2004-01-25 19:57 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 [this message]
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
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=4014209E.2040908@opersys.com \
--to=karim@opersys.com \
--cc=da-x@gmx.net \
--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