From: "J . A . Magallon" <jamagallon@able.es>
To: Zack Brown <zbrown@tumblerings.org>
Cc: "David L . Nicol" <david@kasey.umkc.edu>,
linux-cluster@nl.linux.org, riel@conectiva.com.br,
viro@math.psu.edu,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Will Mosix go into the standard kernel?
Date: Tue, 27 Feb 2001 23:33:56 +0100 [thread overview]
Message-ID: <20010227233356.A1400@werewolf.able.es> (raw)
In-Reply-To: <3A9C1A3A.8BC1BCF2@kasey.umkc.edu> <Pine.LNX.3.96.1010227134555.780R-100000@renegade>
In-Reply-To: <Pine.LNX.3.96.1010227134555.780R-100000@renegade>; from zbrown@tumblerings.org on Tue, Feb 27, 2001 at 22:56:25 +0100
On 02.27 Zack Brown wrote:
> Do the Mosix folks have anything to add about possible integration into the
> kernel? (should have cced them earlier, but it slipped my mind)
>
And also beowulf people, beowulf@beowulf.org.
--
J.A. Magallon $> cd pub
mailto:jamagallon@able.es $> more beer
Linux werewolf 2.4.2-ac5 #1 SMP Tue Feb 27 01:09:47 CET 2001 i686
next prev parent reply other threads:[~2001-02-27 22:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 17:17 Will Mosix go into the standard kernel? Zack Brown
2001-02-27 21:20 ` David L. Nicol
2001-02-27 21:32 ` Rik van Riel
2001-02-28 23:06 ` Daniel Ridge
2001-02-28 23:58 ` Albert D. Cahalan
2001-03-01 0:53 ` Dan Hollis
2001-03-01 1:35 ` Daniel Ridge
2001-03-01 2:37 ` zbrown
2001-03-02 0:52 ` Pavel Machek
2001-02-27 21:37 ` Alexander Viro
2001-02-27 21:56 ` Zack Brown
2001-02-27 22:29 ` zbrown
2001-02-27 22:33 ` J . A . Magallon [this message]
2001-02-28 17:59 ` Ric Wheeler
-- strict thread matches above, loose matches on Subject: below --
2001-02-27 17:31 Christopher Chimelis
2001-02-27 17:40 ` Zack Brown
[not found] <fa.o4k0c0v.smgv2v@ifi.uio.no>
[not found] ` <fa.m9jgfcv.17n8s2n@ifi.uio.no>
2001-03-01 15:02 ` Tor Arntsen
2001-03-01 19:13 ` Tim Wright
2001-03-02 10:22 Tor Arntsen
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=20010227233356.A1400@werewolf.able.es \
--to=jamagallon@able.es \
--cc=david@kasey.umkc.edu \
--cc=linux-cluster@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=viro@math.psu.edu \
--cc=zbrown@tumblerings.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.