My openSUSE systems just received a kernel update. Normally that requires a reboot, but not this time. Why not? I'm running openSUSE 13.1. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Apr 28, 2016 at 09:45:35PM -0400, James Knott wrote:
My openSUSE systems just received a kernel update. Normally that requires a reboot, but not this time. Why not? I'm running openSUSE 13.1.
it does require a reboot. The patch had the reboot_needed flag, so zypper should have output the recommendation to reboot. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
My openSUSE systems just received a kernel update. Normally that requires a reboot, but not this time. Why not? I'm running openSUSE 13.1.
Might you already have had that update installed? There was an issue with 3.12 being overwritten/deleted and having to be re-issued. It was discussed on opensuse-evergreen this week. -- Per Jessen, Zürich (4.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/28/2016 09:45 PM, James Knott wrote:
My openSUSE systems just received a kernel update. Normally that requires a reboot, but not this time. Why not? I'm running openSUSE 13.1.
Its not "13.1" that matters AFAIK. When the 4.x series was released part of its bragging DNA was that it could patch the kernel with no need for a reboot. If you're running the 3.x series kernel distributed with 13.1 then of course you need a reboot :-) If you're running a 4.x series kernel and it gets updates then this is a perfectly valid question. HOWEVER .. Yes, as regular readers will recall, I'm running the 4.5 kernel from the Kernel_Stable repository and so far all the updates have required a reboot. When I attend Suse Days, the bragging about the product still mentions not shutdown/reboot as a feature of the Linux kernel. Is this something we can only expect with LEAP? Why not the other series 4. kernel users? Is it something that the Suse build has decided not to partake of, that all kernel updates MUST require a reboot? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 04/28/2016 09:45 PM, James Knott wrote:
My openSUSE systems just received a kernel update. Normally that requires a reboot, but not this time. Why not? I'm running openSUSE 13.1.
Its not "13.1" that matters AFAIK.
When the 4.x series was released part of its bragging DNA was that it could patch the kernel with no need for a reboot.
If you're running the 3.x series kernel distributed with 13.1 then of course you need a reboot :-)
If you're running a 4.x series kernel and it gets updates then this is a perfectly valid question.
HOWEVER .. Yes, as regular readers will recall, I'm running the 4.5 kernel from the Kernel_Stable repository and so far all the updates have required a reboot.
When I attend Suse Days, the bragging about the product still mentions not shutdown/reboot as a feature of the Linux kernel.
Is this something we can only expect with LEAP? Why not the other series 4. kernel users? Is it something that the Suse build has decided not to partake of, that all kernel updates MUST require a reboot?
Sofar it seems to be SLES(12) only: http://www.zdnet.com/article/no-reboot-patching-comes-to-linux-4-0/ http://www.zdnet.com/article/suse-gets-live-patching/
To deploy and use it today, SUSE customers must have a corresponding SLES 12 Priority Support subscription and Primary or Designated Support Engineer service from SUSE.
-- Per Jessen, Zürich (10.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Apr 29, 2016 at 12:10:46PM +0200, Per Jessen wrote:
Anton Aylward wrote:
On 04/28/2016 09:45 PM, James Knott wrote:
My openSUSE systems just received a kernel update. Normally that requires a reboot, but not this time. Why not? I'm running openSUSE 13.1.
Its not "13.1" that matters AFAIK.
When the 4.x series was released part of its bragging DNA was that it could patch the kernel with no need for a reboot.
If you're running the 3.x series kernel distributed with 13.1 then of course you need a reboot :-)
If you're running a 4.x series kernel and it gets updates then this is a perfectly valid question.
HOWEVER .. Yes, as regular readers will recall, I'm running the 4.5 kernel from the Kernel_Stable repository and so far all the updates have required a reboot.
When I attend Suse Days, the bragging about the product still mentions not shutdown/reboot as a feature of the Linux kernel.
Is this something we can only expect with LEAP? Why not the other series 4. kernel users? Is it something that the Suse build has decided not to partake of, that all kernel updates MUST require a reboot?
Sofar it seems to be SLES(12) only:
http://www.zdnet.com/article/no-reboot-patching-comes-to-linux-4-0/ http://www.zdnet.com/article/suse-gets-live-patching/
We are doing this for SLES 12 currently, yes. The patches are being manually developed for every kernel we released, we target important security issues only. To give you an estimate, it takes around 1+ week for such a patch to be developed and it then is largely confined to the 3.12 codebase we use there. It is nothing generic or fully automated as you might probably think of. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Anton Aylward -
James Knott -
Marcus Meissner -
Per Jessen