{"id":36281,"date":"2019-10-31T22:10:39","date_gmt":"2019-10-31T19:10:39","guid":{"rendered":"https:\/\/prohoster.info\/blog\/spravochnaya-chego-zhdat-ot-fedora-silverblue\/"},"modified":"2019-10-31T22:10:39","modified_gmt":"2019-10-31T19:10:39","slug":"spravochnaya-chego-zhdat-ot-fedora-silverblue","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/spravochnaya-chego-zhdat-ot-fedora-silverblue","title":{"rendered":"Guide: What to Expect from Fedora Silverblue","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Exploring the Features of an Immutable OS.<\/h5>\n

\n\"Guide:<\/a><\/noindex>
\n\/ \u0444\u043e\u0442\u043e Clem Onojeghuo<\/a><\/noindex> Unsplash<\/i><\/p>\n

How Silverblue Came to Be<\/h2>\n

\nFedora Silverblue is an immutable desktop operating system. All applications run in isolated containers, and updates are installed atomically.<\/p>\n

Previously, the project was called Fedora Atomic Workstation<\/a><\/noindex>. It was later renamed Silverblue. According to the developers, they considered over 150 name options. Silverblue was chosen simply because there was a free domain and social media accounts available.<\/a><\/noindex><\/p>\n

The updated system replaced<\/a><\/noindex> Fedora Workstation as the priority build for desktops in Fedora 30. The authors say that in the future, Silverblue might completely replace<\/a><\/noindex> Fedora Workstation.<\/p>\n

One of the residents of Hacker News suggested<\/a><\/noindex>, that the concept of Silverblue evolved from the project Stateless Linux<\/a><\/noindex>. It was promoted in Fedora about ten years ago. Stateless Linux was meant to simplify administration for thin and thick clients. In it, all system configuration files were also opened in 'read-only' mode.<\/p>\n

What 'immutability' Provides<\/h2>\n

\nThe term 'immutable operating system' indicates that the root and user directories are mounted in read-only mode. All mutable data is placed in the \/var directory. A similar method is used by developers of ChromeOS<\/a><\/noindex> and macOS Catalina<\/a><\/noindex>. This approach enhances the security of the OS and prevents the accidental deletion of system files.<\/p>\n

One resident of Hacker News shared in a thematic thread explained<\/a><\/noindex>, that once they accidentally deleted several system files while modifying the Ubuntu Yaru theme. They didn't have backups due to an error in regex. According to them, an immutable OS would have helped avoid problems.<\/p><\/blockquote>\n

\nUpdating is simplified as well \u2014 you just need to reboot the system with a new image. Additionally, it becomes possible to quickly switch between several branches (releases of Fedora). For instance, between the currently developed version of Fedora Rawhide<\/a><\/noindex> and the repository updates-testing<\/a><\/noindex> with upcoming updates.<\/p>\n

What are the Differences from Classic Fedora<\/h2>\n

\nTo install the base environment (\/ and \/usr), the OSTree technology is used. It's fair to say that this is a 'versioning' system for RPM<\/a><\/noindex>-packages. RPM packages are streamed to the OSTree repository using rpm-ostree. When installing a package, it generates<\/a><\/noindex> a restore point to revert to in case of failure.<\/p>\n

OSTree also , rather than taking focus.<\/a><\/noindex> installs applications from dnf\/yum repositories and repositories not supported by Fedora. Instead of the dnf install command, rpm-ostree install should be used. The system will create a new base image of the operating system and replace the installed one.<\/p>\n

As a mechanism for updating applications, Flatpak<\/a><\/noindex>. It runs them in containers. A Flatpak package includes only application-specific dependencies. All base libraries (like GNOME and KDE libraries) remain connectable runtime environments. This approach reduces package size by excluding duplicate components.<\/p>\n

\"Guide:
\n\/ \u0444\u043e\u0442\u043e Jonathan Larson<\/a><\/noindex> Unsplash<\/i><\/p>\n

To install applications that are not packaged in Flatpak, you can use Toolbox<\/a><\/noindex>. It allows you to create a container with the classic Fedora installer.<\/p>\n

Similar solutions<\/h2>\n

\nThere are also other distributions whose tasks are similar to Silverblue. An example is MicroOS<\/a><\/noindex> from openSUSE. It is not a standalone distribution but part of the openSUSE Kubic platform for deploying CaaS (Container as a Service).<\/p>\n

The system works with Docker containers. Their images are distributed as RPM packages. This simplifies<\/a><\/noindex> the installation of command-line applications that are not available in Flatpak format. The host system for running containers is formed based on the official repository openSUSE Tumbleweed<\/a><\/noindex>.<\/p>\n

MicroOS was developed for deployment in large-scale environments (such as data centers) but can also operate on single machines.<\/p>\n

An example of another similar development could be . By default, a trimmed version of postmarketOS is preinstalled, designed for testing basic subsystems. The software environment can be loaded directly from the SD card without the need to carry out a firmware update.<\/a><\/noindex>. This is a Linux distribution based on the Nix package manager. Its main feature is the declarative description of configurations. The administrator does not need to manually install and configure the system. The state is specified in a special file: it lists all packages and authentication settings. Then, the package manager automatically brings the OS to the specified state.<\/p>\n

This system is actively use<\/a><\/noindex> used by cloud providers, universities, and IT companies.<\/p>\n

In any case, Silverblue has a chance to carve out its niche in the market. Whether it will succeed remains to be seen in the future.<\/p>\n

\nMaterials from the First blog about corporate IaaS:<\/b><\/p>\n