@SmoochyPit@beehaw.org to 196English • 10 months agoLinux Rulesbeehaw.orgimagemessage-square43fedilinkarrow-up1395
arrow-up1395imageLinux Rulesbeehaw.org@SmoochyPit@beehaw.org to 196English • 10 months agomessage-square43fedilink
minus-square@Rescuer6394@feddit.nllinkfedilink6•10 months agoon a serious note, is possible to never reboot? like an high availability server that can’t never go down, how do they manage kernel updates? * yes i know that now there is kube and docker etc and you can update the container with zero downtime. but how they did it 10 years ago?
minus-squarezealinkEnglish8•10 months agoKernel live patching, which basically rewires kernel functions at runtime, lets you update the kernel without rebooting. I don’t remember how old that is though.
minus-squarenarsheelinkfedilink4•10 months agoYou can go without rebooting if you always have power, don’t care about updates (security) and don’t run into bugs. It’s done with multiple servers I guess. One updates/reboots while the other ones don’t.
on a serious note, is possible to never reboot?
like an high availability server that can’t never go down, how do they manage kernel updates? *
Kernel live patching, which basically rewires kernel functions at runtime, lets you update the kernel without rebooting. I don’t remember how old that is though.
there’s also kexec
That’s still downtime, it just doesn’t reboot firmware
You can go without rebooting if you always have power, don’t care about updates (security) and don’t run into bugs.
It’s done with multiple servers I guess. One updates/reboots while the other ones don’t.