Fellow Fedora Immutable users, have any of you automated your system updates to occur at shutdown? If so, do you find it makes a practical difference?

I’m thinking of doing the same with Tony Walker’s silverblue-update service.

I shutdown most of my machines daily, and that often means getting an updated image shortly after startup the next day and being forced to reboot or nearly always remain one day behind in updates. By checking for updates again at shutdown, this should help ensure I’ve always got the latest daily image at boot. Thoughts?

  • thayer@lemmy.caOPEnglish
    1·
    10 months ago

    I too like to review changes between images, but I’m just as content to run rpm-ostree status and/or rpm-ostree db diff to see what exactly has changed.

    You should be forced to reboot though? And if you don’t want to reboot, can’t you just do an --apply-live?

    I’m hoping to eliminate the extra reboot each day that is usually necessary to activate the latest image. I know that a lot of this will depend on exactly when the image drops from the repos (versus when I shutdown a host), which is why I was looking for some general feedback from others who might have done the same thing…I didn’t know if it’d be worthwhile in the long run, but I guess there’s only one way to find out. As for the --apply-live, I use it on occasion but I don’t want to rely on it for system updates (if that’s even possible).

    • d3Xt3r@lemmy.nz
      1·
      10 months ago

      As for the --apply-live, I use it on occasion but I don’t want to rely on it for system updates (if that’s even possible).

      As I said before, it does work for system updates, the only exception being the kernel. The --apply-live flag was added for that exact reason, to avoid the need for an unnecessary reboot.