public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Zick" <mszick@goquest.com>
To: Rob Landley <landley@trommello.org>,
	zaimi@pegasus.rutgers.edu, linux-kernel@vger.kernel.org
Subject: Re: kernel upgrade on the fly
Date: Wed, 19 Jun 2002 00:09:32 -0500	[thread overview]
Message-ID: <02061900093200.00787@localhost.localdomain> (raw)
In-Reply-To: <20020619010945.6725B7D9@merlin.webofficenow.com>

On Tuesday 18 June 2002 02:37 pm, Rob Landley wrote:
> On Tuesday 18 June 2002 05:21 pm, zaimi@pegasus.rutgers.edu wrote:
> > Hi all,
> >
> >  has anybody worked or thought about a property to upgrade the kernel
> > while the system is running?  ie. with all processes waiting in their
> > queues while the resident-older kernel gets replaced by a newer one.
>
> > Would anybody else think this to be an interesting property to have for
> > the linux kernel or care to comment on this idea?
> >
Sure,
I know two industries that do such a thing (almost);
Spacecraft and the Telephone Company (any/all);

I did say almost...
I'll speak of the telephone industry, because I am more familar with it...
There they use two (or more) machines, running near the same program...
The one connected to the outside world of hardware is duplicating the 
event in a message, sent to the second...
The second, instead of listening to the outside world is listening to the
messages, duplicating all of the program logic except the hardware i/o.
The memory data structures are identical between the two.
When disaster happens...
Machine two rolls out it's listening modules, rolls in the i/o modules,
sends signal to hardware buss switch to give it the system buss.
Then the fun begins... 
Recover the hardware (or at least the billing information).
Note the three points above:
1) Near identical programs
2) Identical data structures
3) Two sets of CPU hardware

Switching from linux-2.4.x to linux-2.6.x doesn't qualify;

The person who asked this question wants to do it on
a single machine - The price just went way up...

Linux uses internal data structures when and wherever
they are needed.  Updating them all to be consistant 
would be a real b....
Probably you would have to start from scratch and
rebuild them...

Hmm, I think I just said "reboot" the machine with 
the new kernel.

Mike

  reply	other threads:[~2002-06-19  5:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 21:21 kernel upgrade on the fly zaimi
2002-06-18 19:37 ` Rob Landley
2002-06-19  5:09   ` Michael S. Zick [this message]
2002-06-19 17:22   ` John Alvord
2002-06-19 16:56     ` Rob Landley
2002-06-22  8:40       ` Pavel Machek
2002-06-22  8:34   ` Pavel Machek
2002-06-18 21:30 ` Russell King
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 20:19 zaimi
2002-06-21 13:42 ` Rob Landley
2002-06-20 20:40 Jesse Pollard

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=02061900093200.00787@localhost.localdomain \
    --to=mszick@goquest.com \
    --cc=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaimi@pegasus.rutgers.edu \
    /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