From: Pavel Machek <pavel@ucw.cz>
To: Jeff Arnold <jbarnold@ksplice.com>
Cc: linux-kernel@vger.kernel.org, tabbott@ksplice.com,
wdaher@ksplice.com, andersk@ksplice.com, nelhage@ksplice.com,
price@ksplice.com, geofft@ksplice.com
Subject: Re: Ksplice updates for Ubuntu 9.04 Jaunty
Date: Tue, 30 Jun 2009 08:31:52 +0200 [thread overview]
Message-ID: <20090630063152.GC1351@ucw.cz> (raw)
In-Reply-To: <alpine.DEB.1.10.0906250451210.22588@vinegar-pot.mit.edu>
On Thu 2009-06-25 05:51:56, Jeff Arnold wrote:
> Hello,
>
> The Ksplice team [1] is now providing rebootless kernel updates for Ubuntu
> 9.04 Jaunty to anyone who configures their machine to receive them [2].
> In short, users can click a few buttons and start getting all of the
> Ubuntu kernel security updates applied to their system without rebooting.
> No initial kernel changes are needed.
Nice advertisment...
> Ksplice applies traditional source code patches to unmodified Linux
> kernels. It can be used to apply all of the Linux security patches over
> multiple years [7], and it can also apply reliability patches and other
> bug fixes, such as from the Linux stable tree.
Hmmm, so what are its limits? How much manual work is involved? Lets
say I want 2.6.30 -> 2.6.31-rc1... that's just source patch, right?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-07-01 9:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 9:51 Ksplice updates for Ubuntu 9.04 Jaunty Jeff Arnold
2009-06-30 6:31 ` Pavel Machek [this message]
2009-07-02 19:06 ` Jeff Arnold
2009-07-02 21:38 ` Pavel Machek
2009-07-05 18:28 ` Jeff Arnold
2009-07-05 18:47 ` Pavel Machek
2009-07-06 17:28 ` David Newall
2009-07-07 16:46 ` Nelson Elhage
2009-07-02 23:51 ` KOSAKI Motohiro
2009-07-05 18:31 ` Jeff Arnold
2009-07-06 9:28 ` KOSAKI Motohiro
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=20090630063152.GC1351@ucw.cz \
--to=pavel@ucw.cz \
--cc=andersk@ksplice.com \
--cc=geofft@ksplice.com \
--cc=jbarnold@ksplice.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nelhage@ksplice.com \
--cc=price@ksplice.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.