Linux

47940 readers

1622 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

Silverblue: Run ostree updates at shutdown? (lemmy.ca)

submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 9 months ago* (last edited 9 months ago) (2 children)

I use uBlue and update manually (using a custom alias/script) whenever I get the time, like say during my lunch break or something. Reason being, I actually like watching the update process and seeing what gets updated, watching out for major version number changes or major package upgrades, and if I'm interested I may look up some of their changelogs to find out about their new features etc.

and being forced to reboot

You should be forced to reboot though? And if you don't want to reboot, can't you just do an --apply-live? I mean you'd still need to reboot for a kernel update but for the most part, you should be able to use most of your new packages without a reboot. And this holds true even more so if you're updating Flatpak/container/Nix/pip/cargo/brew packages. And I hope you're not doing the rookie mistake of actually installing stuff at the ostree layer instead of using Flatpaks/containers/Nix etc.

[–] [email protected] 1 points 9 months ago (1 children)

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).

[–] [email protected] 1 points 9 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.