seitanic@lemmy.sdf.org to Linux@lemmy.ml · 1 year agoMicrosoft causes learned helplessnesslemmy.sdf.orgimagemessage-square220fedilinkarrow-up1459arrow-down1125
arrow-up1334arrow-down1imageMicrosoft causes learned helplessnesslemmy.sdf.orgseitanic@lemmy.sdf.org to Linux@lemmy.ml · 1 year agomessage-square220fedilink
minus-squareKubeRoot@discuss.tchncs.delinkfedilinkarrow-up0·1 year agoDoes that update the kernel in-place, or only fix up kernel modules to continue working after the update?
minus-squareOneCardboardBox@lemmy.sdf.orglinkfedilinkEnglisharrow-up2·edit-21 year agoIt moves the old kernel modules to the right location for the old kernel to still find them after you’ve upgraded. When you restart the system to use the new kernel, the old kernel module symlinks are cleaned up. From what I understand, live kernel patching is only recommended for critical security fixes to server environments where you can’t just boot off every user. https://wiki.archlinux.org/title/Kernel_live_patching
Does that update the kernel in-place, or only fix up kernel modules to continue working after the update?
It moves the old kernel modules to the right location for the old kernel to still find them after you’ve upgraded. When you restart the system to use the new kernel, the old kernel module symlinks are cleaned up.
From what I understand, live kernel patching is only recommended for critical security fixes to server environments where you can’t just boot off every user. https://wiki.archlinux.org/title/Kernel_live_patching