From: Pavel Machek <pavel@suse.cz>
To: Karim Yaghmour <karim@opersys.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Adeos <adeos-main@mail.freesoftware.fsf.org>,
Philippe Gerum <rpm@xenomai.org>
Subject: Re: [PATCH] Adeos nanokernel for 2.5.38 1/2: no-arch code
Date: Wed, 25 Sep 2002 10:17:00 +0200 [thread overview]
Message-ID: <20020925081700.GA4778@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <3D90F3AC.84AFDE93@opersys.com>
Hi!
> > You can't
> > run two copies of linux, because they would fight over memory; right?
>
> Currently we can't, you're right. But I've already detailed how to do
> this in a paper I wrote last july on how to obtain Linux SMP clusters
> with as few modifications to the kernel as possible. The paper is
> available on the web:
> http://opersys.com/ftp/pub/Adeos/practical-smp-clusters.ps
> (If you stil can't access the web as said in the other email, I can
> send you a copy off-list if you want.)
Its okay now, thanx.
> > Do you have something that can run alongside linux?
>
> Certainly. According to some reports it's already used in some commercial
> systems and, as today's RTAI announcement reads, it will be the basis
> for the next release of RTAI.
Ok. Good luck pushing it through linus ;-).
Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.
next prev parent reply other threads:[~2002-09-25 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 2:58 [PATCH] Adeos nanokernel for 2.5.38 1/2: no-arch code Karim Yaghmour
2002-09-22 4:59 ` Pavel Machek
2002-09-24 21:05 ` Karim Yaghmour
2002-09-24 21:33 ` [Adeos-main] " Jacob Gorm Hansen
2002-09-24 23:15 ` Karim Yaghmour
2002-09-24 22:06 ` Pavel Machek
2002-09-24 23:22 ` Karim Yaghmour
2002-09-25 8:17 ` Pavel Machek [this message]
2002-09-23 3:03 ` Arnaldo Carvalho de Melo
2002-09-23 3:09 ` Karim Yaghmour
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=20020925081700.GA4778@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--cc=adeos-main@mail.freesoftware.fsf.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpm@xenomai.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 NNTP newsgroup(s).