| |||||||||||||
Ksplice and kreplaceKsplice and kreplacePosted Nov 27, 2008 13:02 UTC (Thu) by vonbrand (subscriber, #4458)Parent article: Ksplice and kreplace
I worry about any mechanisms that will by force be very rarely used in earnest, and that just can't really be tested for that exact use case before live use. This is just an invitation to trigger Murphy's law. If the machine is really that indispensable, it should be well protected, and some fail-over provisions should be in place, its applications presumably would be set up to checkpoint and restart; all this regardless of any kernel-replace-while-running wizardry. This problem space has other, well-tested (but sadly much less geeky and exciting) solutions at hand, and has had for some time.
(Log in to post comments)
Ksplice and kreplace Posted Nov 27, 2008 17:02 UTC (Thu) by ewan (subscriber, #5533) [Link] some fail-over provisions should be in place, its applications presumably would be set up to checkpoint and restartIt's not always quite that simple. That sort of thing can work well for services with relatively little state, accessed over the network, but it doesn't work so well for things like desktop systems that tend to have applications with lots of unique in-memory state, persistent network connections etc. Now, you might think that rebooting a personal desktop isn't such a big deal, but imagine it's a terminal server with sessions running for tens of users, and an update comes out for a local root hole. You've either got the choice of chucking all your users off (quite possibly to another system, but it's still disruptive) or leaving the hole unpatched, neither of which options are terribly appealing. This sort of live patching approach offers a potential way out.
People upgrade their kernels all the time Posted Dec 3, 2008 12:53 UTC (Wed) by walles (guest, #954) [Link] I worry about any mechanisms that will by force be very rarely used in earnestPeople upgrade their kernels all the time. People generally don't like re-booting their machines. Why are you worrying that this feature would be "very rarely used"? Cheers //Johan
|
|||||||||||||