public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Aloni <da-x@gmx.net>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Cooperative Linux
Date: Sun, 25 Jan 2004 21:35:18 +0200	[thread overview]
Message-ID: <20040125193518.GA32013@callisto.yi.org> (raw)

Hello fellow developers, kernel hackers, and open source contributors,

Cooperative Linux is a port of the Linux kernel which allows it 
to run cooperatively under other operating systems in ring0 without 
hardware emulation, based on very minimal changes in the architecture 
dependent code and almost no changes in functionality.

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

Our motto is:

    "If Linux runs on every architecture, why should another 
     operating system be in its way?"

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. 

Cooperative Linux is like the kernel mode equivalent of User Mode Linux. 
It relies on the host OS kernel-space interfaces rather than relying on 
host OS user-space interfaces.

Currently, it is stable enough (on some common hardware configurations) 
for running a fully functional KNOPPIX/Debian system on Windows (see 
website screen-shots).

Another project close to achieving that goal is the Windows port of 
User Mode Linux (http://umlwin32.sf.net).

Project page:

    http://sourceforge.net/projects/colinux 

Thank you for your time,

 - The coLinux development team.

This Open Source project is sponsored and produced by AIST, 2004 
http://www.aist.go.jp/

-- 
Dan Aloni
da-x@gmx.net

             reply	other threads:[~2004-01-25 19:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 19:35 Dan Aloni [this message]
2004-01-25 20:01 ` [ANNOUNCE] Cooperative Linux 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
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=20040125193518.GA32013@callisto.yi.org \
    --to=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