News for hackers. Stuff that matters.
Re:Ksplice: Automatic Rebootless Kernel Updates (2008) [pdf] by tzs on Friday August 15, 2014 @07:43PM (#8184898)
There are at least two reasons to restart something after you update it.

(1) the update could not be applied to the running instance, so you have to restart to put the update into service, and

(2) to demonstrate that the update did not break the ability of the thing to start.

This address #1. It does not address #2.

It is extremely annoying if something has run for a year with a couple dozen live updates applied without restarting and then you have to restart for some reason (power failure, perhaps), and then you discover that somewhere in the last year it lost the ability to start. I'd much rather discover that an update has introduced a problem with startup immediately after applying the update.

Restarting things should be a regular part of maintenance.

Re:Ksplice: Automatic Rebootless Kernel Updates (2008) [pdf] by SoftwareMaven on Friday August 15, 2014 @08:07PM (#8184960)
When you restart, you will restart into whichever kernel you have installed, which may be whatever you booted into previously or a new distro kernel with the updates compiled in. There are no Ksplice updates loaded until you tell them to load and Ksplice does not make any modifications to the actual Kernel binary, so #2 isn't really an issue. The real problem is there may be limitations on when you can reboot, leaving you in a vulnerable state. Sure, an ideal environment would let you reboot any system at any time, but those places are like unicorn ranches.

I completely agree with your last comment, though: systems suffer from weird bit-rot diseases. If you never reboot, you may find things challenging when you finally have to.

Disclosure: I work on the Ksplice team.

Re:Ksplice: Automatic Rebootless Kernel Updates (2008) [pdf] by jdhendrickson on Friday August 15, 2014 @11:34PM (#8185320)
How do you feel about Oracles handling of the code?
Re:Ksplice: Automatic Rebootless Kernel Updates (2008) [pdf] by SoftwareMaven on Friday August 15, 2014 @11:56PM (#8185364)
I've worked with a lot of good teams over the years. I've worked with two great teams: The League of Legends team at Riot Games and the Ksplice team at Oracle. I know what many people think of when they think of an average engineer at a huge company such as Oracle, but this team is about as far from stereotypical as you can get.
Re:Ksplice: Automatic Rebootless Kernel Updates (2008) [pdf] by fragmede on Friday August 15, 2014 @08:13PM (#8184969)
I'm not seeing #2:

Step 1. Boot your version 1 kernel.

time passes, and version 2 is released

Step 2. Apply Ksplice updates to bring your kernel up to version 2.

Your system reboots (let's say due to a power failure):

Step 1. Boot your version 1 kernel. This boots because it's the same kernel you booted a year ago.

Step 2. (Before bringing up the network) Apply ksplice updates to bring your kernel to version 2. This works because you booted the same version 1 kernel, and the updates haven't changed either.

Re:Ksplice: Automatic Rebootless Kernel Updates (2008) [pdf] by IvyMike on Friday August 15, 2014 @08:50PM (#8185031)
I used to reboot my Solaris workstation once a month. A friend mocked me--"Still in that Windows mentality". I replied, "No, I reboot it to make sure I still can".

When he rebooted his machine (after almost a year) and it failed to come up, I got to mock him back. "So can you remember what changes you made... in the last year".

On the other hand, even though I've never used it, ksplice must be a nifty way to apply urgent updates between regularly scheduled reboots.

Re:Ksplice: Automatic Rebootless Kernel Updates (2008) [pdf] by tedks on Friday August 15, 2014 @10:30PM (#8185215)
Even with a dynamic software updating system in place, you shouldn't be deploying dynamic updates directly to production without testing them. It'd be pretty stupid to deploy an update by any mechanism that would render a service unstartable.