Also, I see live kernel patching as a basic desktop usability feature, not a server feature. If you have a mission critical server and you don't have a good plan for what to do while it's shut down, you're doing it wrong. Rebooting is far more of a hardship for desktop users than server users.
Announcement
Collapse
No announcement yet.
Linux 5.2 To Enable GCC 9's Live-Patching Option, Affecting Performance In Select Cases
Collapse
X
-
This gives new meaning to distro dogfood. I can build my kernels however I want, including manual intervention for some unwanted options that are forced, but the poor sods that have to use distro kernels get a shit sandwich these days.
- Likes 2
Comment
-
Originally posted by M@GOid View PostIf I not mistaken, Canonical offers paid support for live patches. Lets see if they will let this free option on by default in future releases.
Consider that for a patch P, they'll have to create separate live-patches for all kernels X.Y.Z-N in their repo, and maybe even different versions depending on whether X.Y.Z-N is a pristine kernel or whether it has already has previous live-patches P1, P2, P3 applied to it. In the end you'll have quite many live-patches to keep track of and test.
Comment
-
Originally posted by MaxToTheMax View PostAlso, I see live kernel patching as a basic desktop usability feature, not a server feature. If you have a mission critical server and you don't have a good plan for what to do while it's shut down, you're doing it wrong. Rebooting is far more of a hardship for desktop users than server users.
Time to start compiling all kernels from now on, just to be safe from cancer.
Comment
-
Originally posted by MaxToTheMax View PostRealistically, to get everything back to how I had it so I can continue getting work done, rebooting takes about an hour, even though my boot time is only a few seconds.
Comment
-
Originally posted by MaxToTheMax View PostAlso, I see live kernel patching as a basic desktop usability feature, not a server feature. If you have a mission critical server and you don't have a good plan for what to do while it's shut down, you're doing it wrong. Rebooting is far more of a hardship for desktop users than server users.
What actually needs uptime and kernel patches without rebooting are servers where you can't just reboot the server whenever there is a critical kernel update as you have to plan the reboots months ahead to avoid disrupting the service.
Then you can use this feature wherever you feel like it, and none will stop you, but don't claim this bs please.
- Likes 1
Comment
-
Originally posted by starshipeleven View PostNo offence, but if you "need" to have hundreds of tabs open, a movie player and many editors and IDEs open at the same time to be productive you are probably deluding yourself.
And yes, if I had to open everything from scratch at work every day, that's 20-60 fewer minutes a day for doing work.Last edited by MaxToTheMax; 10 April 2019, 10:09 PM.
- Likes 1
Comment
-
Originally posted by starshipeleven View PostBullshit, you are a very atypical desktop user, most people does not have hundreds of applications open.
What actually needs uptime and kernel patches without rebooting are servers where you can't just reboot the server whenever there is a critical kernel update as you have to plan the reboots months ahead to avoid disrupting the service.
Then you can use this feature wherever you feel like it, and none will stop you, but don't claim this bs please.Last edited by MaxToTheMax; 10 April 2019, 10:34 PM.
Comment
-
Originally posted by guidotrueb View PostAll this and we still don't have proper hibernate/resume support... =/
Comment
Comment