On Mon, Jun 29, 2009 at 10:58 PM, Bill McGonigle <bill@xxxxxxxxxxxxxxxx> wrote:
On 06/29/2009 10:49 PM, Kevin Kofler wrote:And to date there hasn't really been any compelling reason to issue tiny
> It can only handle small patches which don't change
> any data structures. So the official Fedora kernel updates will never be
> suitable to be distributed through KSplice.
patch security-updated kernels, 'cause you have to reboot anyway, right?
But as the technology improves, more opportunities arise.
I recall deploying some sort of hack workaround for the vmsplice exploit
a while back on a whole bunch of machines (Fedora or downstreams) that
were going to need a reboot scheduled up to a week in the future. This
kind of technology would have been really swell to have then.
Lots of reasons to not want to reboot machines - most of the arguments
for supporting laptop suspend would fit. Some of them may fall into the
"protecting users from themselves" category, but that's not a bad thing
either.
-Bill
--
Bill McGonigle, Owner Work: 603.448.4440
BFC Computing, LLC Home: 603.448.1668
http://www.bfccomputing.com/ Cell: 603.252.2606
Twitter, etc.: bill_mcgonigle Page: 603.442.1833
Email, IM, VOIP: bill@xxxxxxxxxxxxxxxx
Blog: http://blog.bfccomputing.com/
VCard: http://bfccomputing.com/vcard/bill.vcf
Also, while KSplice is currently being used for kernel updates, it isn't limited to those. It could be adapted to work for other updates that normally force a reboot. Though, I can't think of any off the top of my head, it has been over a week since I ran the updater...
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
