From: Jim Richardson <warlock@eskimo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Hot kernel change
Date: Fri, 20 Feb 2004 03:06:49 -0800 [thread overview]
Message-ID: <20040220110649.GA24361@hockwold.net> (raw)
In-Reply-To: <30562.62.229.71.110.1077222343.squirrel@webmail.r3pek.homelinux.org>
On Thu, Feb 19, 2004 at 08:25:43PM -0000, Carlos Silva wrote:
<snip>
>well, that's what i had in mind... if this could be possible under x86
>would be great. i say x86 'cause for what a read, MkLinux looks like a
>MacLinux Distribution, correct me if i am wrong.
>like i said in the first place, i don't program for the kernel (yet, i
>intend to), so i don't know what are the big/small changes that have to be
>made for somthing like this to work. but i would really like to see this
>working :D
MkLinux was available for x86, but I have no idea if it is still in
development. To be clear, it doesn't allow you to simply replace a
kernel, but to add a second one, and possibly, to start transferring
over tasks to it.
You can do much the same thing with user mode linux also. Again, not a
kernel replacement in that sense, but something similar, sort of.
--
Jim Richardson http://www.eskimo.com/~warlock
RFC 882 put the dot in .com.
next prev parent reply other threads:[~2004-02-20 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 13:33 Hot kernel change Carlos Silva
2004-02-19 14:05 ` Richard B. Johnson
2004-02-19 20:04 ` Jim Richardson
2004-02-19 20:25 ` Carlos Silva
2004-02-20 11:06 ` Jim Richardson [this message]
2004-02-20 13:03 ` Nigel Rantor
2004-02-19 21:08 ` Randy.Dunlap
2004-02-19 21:32 ` Carlos Silva
2004-02-20 7:17 ` Dominik Kubla
-- strict thread matches above, loose matches on Subject: below --
2004-04-02 16:16 Yann Dirson
2004-04-02 16:45 ` Steven Cole
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=20040220110649.GA24361@hockwold.net \
--to=warlock@eskimo.com \
--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