From: "Chris Friesen" <cfriesen@nortel.com>
To: balbir@linux.vnet.ibm.com
Cc: ananth@in.ibm.com, Nikanth Karthikesan <knikanth@suse.de>,
linux-kernel@vger.kernel.org, davem@davemloft.net,
mhiramat@redhat.com, contact@ksplice.com, jbarnold@ksplice.com,
tabbott@ksplice.com, wdaher@ksplice.com, andersk@ksplice.com
Subject: Re: [RFC] kreplace: Rebootless kernel updates
Date: Fri, 21 Nov 2008 11:29:16 -0600 [thread overview]
Message-ID: <4926EFEC.3000907@nortel.com> (raw)
In-Reply-To: <4926DC1B.1020809@linux.vnet.ibm.com>
Balbir Singh wrote:
> Undoubtedly, but a good warning is the best way to keep people warned about
> running such code :) It is a useful thing to have and to run, but running it
> would take more guts than anything else.
There is significant demand for this sort of thing in the
telecom/enterprise space, where they would like to apply kernel patches
(especially security patches and bugfixes) with minimal downtime.
Chris
next prev parent reply other threads:[~2008-11-21 17:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 11:50 [RFC] kreplace: Rebootless kernel updates Nikanth Karthikesan
2008-11-21 13:38 ` Ananth N Mavinakayanahalli
2008-11-21 16:04 ` Balbir Singh
2008-11-21 17:29 ` Chris Friesen [this message]
2008-11-24 11:07 ` Nikanth Karthikesan
2008-11-24 11:07 ` Nikanth Karthikesan
2008-11-21 14:39 ` Masami Hiramatsu
2008-11-24 11:07 ` Nikanth Karthikesan
2008-11-24 15:15 ` Masami Hiramatsu
2008-11-26 2:48 ` Nikanth K
2008-11-21 20:19 ` Anders Kaseorg
2008-11-22 3:46 ` Jeff Arnold
2008-11-23 19:39 ` Andi Kleen
2008-11-23 20:53 ` Jeff Arnold
2008-11-24 11:07 ` Nikanth Karthikesan
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=4926EFEC.3000907@nortel.com \
--to=cfriesen@nortel.com \
--cc=ananth@in.ibm.com \
--cc=andersk@ksplice.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=contact@ksplice.com \
--cc=davem@davemloft.net \
--cc=jbarnold@ksplice.com \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=tabbott@ksplice.com \
--cc=wdaher@ksplice.com \
/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