3 ms·
> Who is keeping a Linux machine updated without regular restarts? I've never heard of that. You only need to restart when the kernel has a security update, an
by rbanffy 2y ago
> Who is keeping a Linux machine updated without regular restarts? I've never heard of that.
You only need to restart when the kernel has a security update, and you can do it at your own convenience. Same happens with some fundamental components (such and Gnome session manager). My Fedora box usually has a 30 day-ish uptime. The Ubuntu laptop a little less because of its usage pattern, but it signals when a restart would be a good idea, and leaves the decision to me. When it’s time, shutting down and restarting is just a couple seconds. Fedora is more cautious and does updates on startup or shutdown, and never automatically.
A distro is a curated work. All the bits and pieces are known to work well together. The price is that you might get behind the latest and greatest from time to time. If you are using 20 PPAs or package sources with varying levels of testing, you shouldn’t blame the distro for your self-inflicted wounds. Unless you actually know very well what you’re doing, use the packaged versions. I actually know what I’m doing and I use the packaged versions, because I’m paid to work, not to debug my setup.
> And then some package may either fail to initially install
I had experiences like that with Debian Sid. As is well known to anyone familiar with the Toy Story universe, Sid breaks your toys. I’ve never seen anything like that with Debian testing, Ubuntu, RHEL/Centos/Fedora in the past 20 years or so. But I never actively tried to break the package system by having 20 different sources for stuff.