Rolling Updates and restarts vs major upgrades
by thethinker from LinuxQuestions.org on (#4Y4MM)
I'm sure this discussion has been had around LQ before, but I wasn't able to find anything specific.
I'm having some irritation around how my Xubuntu system handles updates. I use it on a machine which is up and running for 5-6 days at a time (I keep multiple desktops, dedicated browser tabs, etc, and it takes some time every Monday for me to get it set back up). When Xubuntu updates, it gives me a little gui message, updates, and then tells me the system needs to restart to complete updates. I always "restart later" and do it when it's convenient for me, but if the updates are not actually finished that must be a bad habit.
Contrast this with Slackware, which I run at home, and when I do updates (via slackpkg update etc etc), it never tells me it has to restart (except for new releases, I think. The BDFL ensures that's infrequent :-)).
So is there a distinction between OSs that "update like Xubuntu" and those that "update like Slackware", i.e. need to be restarted? Is it simply a feature of "Rolling Updates"?
I'm having some irritation around how my Xubuntu system handles updates. I use it on a machine which is up and running for 5-6 days at a time (I keep multiple desktops, dedicated browser tabs, etc, and it takes some time every Monday for me to get it set back up). When Xubuntu updates, it gives me a little gui message, updates, and then tells me the system needs to restart to complete updates. I always "restart later" and do it when it's convenient for me, but if the updates are not actually finished that must be a bad habit.
Contrast this with Slackware, which I run at home, and when I do updates (via slackpkg update etc etc), it never tells me it has to restart (except for new releases, I think. The BDFL ensures that's infrequent :-)).
So is there a distinction between OSs that "update like Xubuntu" and those that "update like Slackware", i.e. need to be restarted? Is it simply a feature of "Rolling Updates"?