From: Russell King <rmk@arm.linux.org.uk>
To: zaimi@pegasus.rutgers.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel upgrade on the fly
Date: Tue, 18 Jun 2002 22:30:08 +0100 [thread overview]
Message-ID: <20020618223008.A17795@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.GSO.4.44.0206181703540.26846-100000@pegasus.rutgers.edu>; from zaimi@pegasus.rutgers.edu on Tue, Jun 18, 2002 at 05:21:49PM -0400
On Tue, Jun 18, 2002 at 05:21:49PM -0400, zaimi@pegasus.rutgers.edu wrote:
> 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.
This has been discussed over and over and over and over and over and over
and over and over and over and over and over and over and over and over
here; typically it comes up about once every six months. Please see
the FAQ: http://www.tux.org/lkml or alternatively search the lkml
archives.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-06-18 21:30 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
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 [this message]
-- 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=20020618223008.A17795@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--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