From: Christopher Chimelis <Christopher.Chimelis@api-networks.com>
To: "'Zack Brown'" <zbrown@tumblerings.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: Will Mosix go into the standard kernel?
Date: Tue, 27 Feb 2001 12:31:05 -0500 [thread overview]
Message-ID: <051DFF3BBA73D3119A5800A0C95BD021C8F3A0@barracuda.alpha-processor.com> (raw)
> Just curious, are there any plans to put Mosix into the
> standard kernel,
> maybe in 2.5, so folks could just configure it and go? it
> seems that the
> number of people with more than one computer might make this
> a feature many
> would at least want to try, especially if it was available as
> an option by
> default. Is there anything in the Mosix folks' implementation
> that would
> prevent this?
I can't speak for the kernel folks, but has it been ported to
architectures other than i386 yet? Last I heard, it hadn't been,
but that was a very long time ago.
C
next reply other threads:[~2001-02-27 17:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 17:31 Christopher Chimelis [this message]
2001-02-27 17:40 ` Zack Brown
-- strict thread matches above, loose matches on Subject: below --
2001-03-02 10:22 Tor Arntsen
[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-02-27 17:17 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
2001-02-28 17:59 ` Ric Wheeler
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=051DFF3BBA73D3119A5800A0C95BD021C8F3A0@barracuda.alpha-processor.com \
--to=christopher.chimelis@api-networks.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®