![]() ![]() Thus updating the system and all related RPMs needs the command rpm-ostreee update: In fact, on Fedora Silverblue, all images and RPMs baked into it are managed by it. Thus there is a way to install and manage RPMs on top of the OSTree image, but still baked right into it: rpm-ostreee. Unfortunately, not all tools can be packages as flatpak: especially command line tools are currently hardly usable at all as flatpak. The idea is to provide a basic system image to all, and all additional software on top in sandboxed formats like Flatpak. Basically OSTree is a set of libraries and tools which helps to manage images and snapshots. Since we are dealing with immutable images here, another tool to manage them is needed: OSTree. In each case, apps and containers are kept separate from the host system, improving stability and reliability. Finally, Silverblue’s immutable design also makes it an excellent platform for containerized apps as well as container-based software development development. Silverblue’s immutable design is intended to make it more stable, less prone to bugs, and easier to test and develop. The operating system that is on disk is exactly the same from one machine to the next, and it never changes as it is used. This means that every installation is identical to every other installation of the same version. 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. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |