From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Carlos Silva <r3pek@r3pek.homelinux.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hot kernel change
Date: Thu, 19 Feb 2004 09:05:25 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0402190845440.30037@chaos> (raw)
In-Reply-To: <12608.62.229.71.110.1077197623.squirrel@webmail.r3pek.homelinux.org>
On Thu, 19 Feb 2004, Carlos Silva wrote:
> hi,
>
> i would like to know if isn't it possible to implement a hot kernel
> change, i mean, without reboot. i would do it myself if i had the knoledge
> to do it but i'm starting with kernel-level programing now. i think it
> would be possible if we make something like M$'s OS do when it hibernates,
> copy all the memory, registers, etc to the disc and then put all back
> again.
>
> am i dreaming or this is possible? :)
>
> Greetings,
>
> Carlos "r3pek" Silva
Sure it's possible. However, you can't change to a new kernel this
way because the addresses of the hardware devices like the PCI bus
devices may change with a new kernel. Since the displacements of
the kernel's internal workings will change with a new version, there
would need to be considerable work done in re-designing the kernel
so that it wouldn't matter.
The best you can do, right now, is reload the same kernel. It
will take about as much time as a reboot, so why bother? Oh, you
intend to keep the same processes running, do you? You expect to
be writing a letter in X-windows and hit the reset switch, magically
returning to the same state after the machine has a new kernel
installed? Well, well-written software is indistinguishable from
magic, but first you need to find out how to make time run back-
wards because, at the very least, the new kernel will be installed
in the future which means many things will have changed (like
network IP addresses, dynamic routes, remote file discriptors, etc.)
Sounds like a neat project for a College Student who wants to
learn to solve problems they haven't even dreamed of yet.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an Intel Pentium III machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-02-19 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 13:33 Carlos Silva
2004-02-19 14:05 ` Richard B. Johnson [this message]
2004-02-19 20:04 ` Jim Richardson
2004-02-19 20:25 ` Carlos Silva
2004-02-20 11:06 ` Jim Richardson
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
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=Pine.LNX.4.53.0402190845440.30037@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=r3pek@r3pek.homelinux.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®