1 |
> |
2 |
> something even worse. Since rebooting is when those tend to |
3 |
> fail/break/whatever, it is yet another reason I avoid rebooting. |
4 |
|
5 |
|
6 |
I take the opposite approach. If I update the kernel and reboot often, I |
7 |
see the following benefits; |
8 |
- Each increment in version is smaller, therefore there's less change per |
9 |
update, which make it easier to troubleshoot if there's problems |
10 |
- Doing something regularly is practice, and practice makes perfect. If you |
11 |
were to update regularly you would become more proficient and confident |
12 |
with doing the init thingy (initrd?) |
13 |
- If a hardware issue occurs, I find it at a good time when i'm not busy, |
14 |
and have the time to troubleshoot |
15 |
- Getting the benefits of the automated kernel code testing (eg syzbot, |
16 |
KASAN) that is used these days finding issues that then get fixed |
17 |
(including security issues). You'd have to assume that over the overall |
18 |
quality of the kernel is improving at a faster rate now than before those |
19 |
extra checks were in place. |
20 |
|
21 |
At work I have raised tickets to have systems with big uptimes have their |
22 |
hardware status reviewed then restarted, a couple of days before I |
23 |
undertake risky/critical work. That way I can have more confidence in the |
24 |
system's health before starting. The classic one is where OPS haven't |
25 |
noticed that disks in a RAID array have died years ago... |
26 |
|
27 |
Even when I have a power fail here, it makes me very nervous to shutdown. |
28 |
> |
29 |
|
30 |
Another benefit of regular updates would be to reduce stress of deciding to |
31 |
shutdown, as you will have more confidence that the systems are healthy |
32 |
when you need to do it. |
33 |
|
34 |
:) |