Kernel Newbies archive mirror
 help / color / mirror / Atom feed
From: Mario Marietto <marietto2008@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: from CoLinux to MoreLinux :D
Date: Sun, 3 Dec 2023 19:58:23 +0100	[thread overview]
Message-ID: <CA+1FSij7NkK-pFq0QuY=9oks5jeCfaiRcUBXu5iTKbDYKHBzzQ@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1591 bytes --]

Hello.

maybe someone of you know the old project called "coLinux" :


Cooperative Linux is the first working free and open source method for
optimally running Linux on Microsoft Windows natively. More generally,
Cooperative Linux (short-named coLinux) is a port of the Linux kernel that
allows it to run cooperatively alongside another operating system on a
single machine. For instance, it allows one to freely run Linux on Windows
2000/XP/Vista/7, without using a commercial PC virtualization software such
as VMware, in a way which is much more optimal than using any general
purpose PC virtualization software. In its current condition, it allows us
to run the KNOPPIX Japanese Edition on Windows.


CoLinux is very old and not maintained for a lot of time and I'm not
interested in resurrecting it (and I don't have the competences to do
it),BUT I'm interested to gather some information about a similar project
that I have in mind. What about if,instead of having a Linux kernel which
can run Windows cooperatively,we have a Linux kernel that can run more
Linux distributions (maybe only 2 as a starting point,as CoLinux already
does) at the same time,without using virtualization software ? Is the
technology behind Colinux the same that's under the lxc or docker
containers or the WSL2 subsystem ? What are the differences ?

I don't use WSL2,I don't use Windows so much. I like Linux and FreeBSD.
So,an even nicer idea is to create a coLinux variant that allows the Linux
kernel to cooperate with FreeBSD. This is even nicer than making a
cooperation between 2 Linuxes.
-- 
Mario.

[-- Attachment #1.2: Type: text/html, Size: 2416 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2023-12-03 19:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03 18:58 Mario Marietto [this message]
2023-12-04  2:06 ` from CoLinux to MoreLinux :D Richard
2023-12-04  8:57   ` Mario Marietto
2023-12-04 20:01     ` Mario Marietto
2023-12-08  1:14       ` jim.cromie
2023-12-08  8:11         ` Mario Marietto
2023-12-08  9:00           ` Mario Marietto
2023-12-08 11:13           ` Richard
2023-12-08 11:53             ` Mario Marietto
2023-12-09 13:24               ` Mario Marietto
2023-12-09 19:01                 ` Richard
2023-12-10  0:02                   ` Mario Marietto
2023-12-10  0:04                     ` Mario Marietto
2023-12-10  3:57                     ` Richard
2023-12-10  6:07                       ` Mario Marietto

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='CA+1FSij7NkK-pFq0QuY=9oks5jeCfaiRcUBXu5iTKbDYKHBzzQ@mail.gmail.com' \
    --to=marietto2008@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).