From: John Bradford <john@grabjohn.com>
To: anomalous_force@yahoo.com (Anomalous Force)
Cc: riel@conectiva.com.br, wa@almesberger.net, ebiederm@xmission.com,
linux-kernel@vger.kernel.org
Subject: Re: holy grail
Date: Sun, 29 Dec 2002 16:44:07 +0000 (GMT) [thread overview]
Message-ID: <200212291644.gBTGi79G001294@darkstar.example.net> (raw)
In-Reply-To: <20021229155600.95805.qmail@web13204.mail.yahoo.com> from "Anomalous Force" at Dec 29, 2002 07:56:00 AM
> > This has been said before, but "for some reason" everybody
> > who said it went quiet the moment they started working on
> > a patch and have never been heard from again.
> >
> > Either they're still working on the problem (after a four
> > years) or they've moved on to an easier/realistic project.
>
> i have stated this would be extremely difficult. no single person
> could attempt this without the support of the other developers as
> the effort must include all aspects of the kernel to some extent.
> the original discussion for this was to show that kexec() _could_
> become something that is a holy grail amoung kernel developers:
> hot-swap.
Why take the easy road, ( :-) ), and merely make the kernel
hot-swappable? You could use the code from the User Mode Linux
project as a starting point for creating a Meta Kernel Mode linux
project, and run several more kernel images concurrently as user mode
processes of the top-level kernel, and then add necessary to connect
any particular physical hardware to the MKML virtual machines.
Then, you could migrate your applications from kernel to kernel
without ever having to re-boot.
Mainframe power on the desktop :-)
John.
next prev parent reply other threads:[~2002-12-29 16:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 0:51 holy grail Anomalous Force
2002-12-27 4:03 ` Werner Almesberger
2002-12-27 7:21 ` Anomalous Force
2002-12-27 7:37 ` Ingo Oeser
2002-12-27 11:30 ` Werner Almesberger
2002-12-28 16:35 ` Anomalous Force
2002-12-28 20:43 ` Rik van Riel
2002-12-29 15:56 ` Anomalous Force
2002-12-29 16:44 ` John Bradford [this message]
2002-12-30 1:05 ` Alan Cox
2002-12-30 1:32 ` Werner Almesberger
2002-12-30 2:45 ` Jeff Dike
2002-12-30 3:55 ` David Lang
2002-12-30 4:39 ` Anomalous Force
2002-12-30 17:57 ` Eric W. Biederman
2002-12-30 13:30 ` Alan Cox
2002-12-29 23:53 ` Werner Almesberger
2002-12-27 13:24 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-12-30 5:00 Anomalous Force
2002-12-30 6:46 ` Ed Sweetman
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=200212291644.gBTGi79G001294@darkstar.example.net \
--to=john@grabjohn.com \
--cc=anomalous_force@yahoo.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=wa@almesberger.net \
/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