Technically a reboot is only required after kernel or major system update (change). However, there is work to make live kernel updates a posibility in the future. Other things like dbus, samba, xorg, etc. only need to be reloaded after they are updated, it's just faster and easier to reboot sometimes depending on the number of these things that are updated. As far as long up-time numbers, this is usually the case for server systems that remain on long term suported operating systems like debian stable, Centos, etc., that are rearly updated and usually supported for upwards of 3 to 5 years. On these systems updates are only pushed out for security reasons and not because there is a newer version available. In the 20+ years that i've been working on and with Linux based systems, reboots have always been neccessary from time to time, even more so on systems with a rolling release model, or ones that have a 3 to 6 month release cycle like Ubuntu.
[Solved] - Cairo Dock suggests frequent reboot after many package updates
|
« Next Oldest | Next Newest »
|
Possibly Related Threads… | |||||
Thread | Author | Replies | Views | Last Post | |
[solve]maui 2 repository The package cache file is corrupted | kevin_tee | 4 | 14,888 |
23rd May 2017, 9:02 Last Post: leszek |
|
backup and restore brings strange loss of many folders | benit | 6 | 20,831 |
16th April 2017, 3:38 Last Post: kdemeoz |
|
Upgrading qBittorrent in Synaptic Package Manager.[ANSWERED] | karlheinrich | 2 | 9,980 |
3rd January 2017, 11:37 Last Post: karlheinrich |