other operating systems, Silverblue is immutable. With Fedora Silverblue there is an implementation of that approach as a Fedora Workstation spin. With the recent rise of container technologies the idea of immutable systems became prominent again. It is used for years and well known to everyone.Īnd in the end it is analogue to the way Linux distributions are kept up2date for ages now, only the command differs from system to system ( apt-get, etc.) Silverblue: OSTree This is the traditional way to keep a Fedora system up2date. Last metadata expiration check: 0:39:20 ago on Tue 01:03:12 PM CEST. Updating a RPM based system via DNF is easy: With Fedora used as a Workstation system there are two ways to manage system packages, because there are two totally different spins of Fedora: the normal one, traditionally based on DNF and thus comprised out of RPM packages, and the new Fedora Silverblue, based on immutable ostree system images. The Kernel, a system for managing services like systemd, core libraries like libc and so on. System packagesĮach and every system is made up at least of a basic set of software. We will look at them in the rest of the post. However, if you want to know and understand what happens underneath it is good to know the separate CLI commands for all kinds of software resources. Using the GUI alone is sufficient to take care of all update routines. If we have a closer look at the configured repositories in Gnome Software we see that it covers main Fedora repositories, 3rd party repositories, flatpaks, firmware and so on: The user does not even know where those come from. The above screenshot highlights that Gnome Software just shows available updates and can manage those. It checks all sources and just provides the available updates in its single GUI: ![]() But before we dive into detailed CLI commands there is a simple way to do that all in one go: The Gnome Software tool does that for you. To properly update your Fedora system you have to check multiple sources. GUI solution Gnome Software – one tool to rule them all… And lost but not least, Fedora Silverblue does not support DNF at all. Also, many firmware updates are managed via the dedicated management tool fwupd. If all goes well you’ll be able to re-connect within 15-20 minutes.Simple, right? But not these days: Fedora recently added capabilities to install and manage code via other ways: Flatpak packages are not managed by DNF. This will disconnect your remote connection and restart the system, initiating the upgrade process. Now comes the actual upgrade process: dnf system-upgrade reboot If you ever want to clear the cache out, dnf system-upgrade clean will do the trick. Downloaded packages will remain in cache and can be updated if you’re not ready to perform the update immedicable. ![]() ![]() You’ll receive an error if the upgrade is not possible. Replace the number after –releasever= with the version you intend to upgrade to. dnf system-upgrade download -refresh -releasever=34 This step will also be recommended before you execute the next step, which will download all necessary packages that are needed for the upgrade. Next we’ll refresh the whole system before the upgrade process can begin. Here’s how to install it: dnf install dnf-plugin-system-upgrade We only need to do this once, and it will remain in place and update itself for future system upgrades. Prerequisite: we need the system upgrade plugin for this process. ![]() Update all packages for the current version before you start, then restart the system to make sure you’re on the latest kernel. In-place upgrades work as far as two versions back, anything further will require intermediate steps. For this example I’m using Fedora 33, and will describe how to upgrade to 34.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |