On Sun, Dec 29, 2019 at 3:52 PM Chris Murphy <li...@colorremedies.com> wrote: > > There are a couple of long term solutions for the problem, depending > on what's being updated. For applications, flatpak can handle updates > (I'm not absolutely sure to what degree it's intended for and reliably > handles updating running applications, but I do it fairly regularly > and haven't seen any ensuing weirdness; the new version is available > at next launch). For the OS itself, rpm-ostree does an out of band > update (uses hard links to created a copy of the operating system, and > then updates that copy), you see the updates upon reboot which you can > do at your liesure. And openSUSE variant doing transactional updates > using Btrfs: basically it makes a snapshot of the operating system, > and applies the updates to the snapshot, and upon reboot it boots the > updated snapshot.
Also useful is 'gsettings set org.gnome.software download-updates false' That'll prevent packagekit/gnome-software from downloading update RPMs, and you can just use 'dnf update' and suffer the consequences of not rebooting soon after. I do this and sometimes suffer, but I've signed up for that, and also, I always take a btrfs snapshot before every update - so I don't really care that much if it blows up.
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
