{"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\/sl\/blog\/administrirovanie\/spravochnaya-chego-zhdat-ot-fedora-silverblue","title":{"rendered":"Referenca: Kaj pri\u010dakovati od Fedora Silverblue","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Raziskujemo zna\u010dilnosti nespremenljivega operacijskega sistema.<\/h5>\n

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

Kako je nastal Silverblue<\/h2>\n

\nFedora Silverblue je nespremenljiv namizni operacijski sistem. V njem se vse aplikacije izvajajo v izoliranih kontejnerjih, posodobitve pa se name\u0161\u010dajo atomsko.<\/p>\n

Prej je projekt nosil ime Fedora Atomic Workstation<\/a><\/noindex>. Kasneje so ga preimenovali v Silverblue. Po besedah razvijalcev so preu\u010dili ve\u010d kot 150 mo\u017enosti imen. Silverblue so izbrali preprosto zato, ker je bil prost domenski naslov in ra\u010duni na dru\u017ebenih omre\u017ejih.<\/a><\/noindex><\/p>\n

Posodobljen sistem je zamenjal<\/a><\/noindex> Fedora Workstation kot prioritetno razli\u010dico za namizja v Fedora 30. Avtorji pravijo, da lahko v prihodnosti Silverblue popolnoma nadomesti<\/a><\/noindex> Fedora Workstation.<\/p>\n

Eden od \u010dlanov Hacker News je predlagal<\/a><\/noindex>, da je koncept Silverblue razvoj projekta Stateless Linux<\/a><\/noindex>. Ta je bila v Fedorah promovirana pred pribli\u017eno desetimi leti. Stateless Linux bi moral poenostaviti upravljanje tankih in debelih odjemalcev. V njem so se tudi vsi konfiguracijski datoteki sistema odpirali v na\u010dinu 'samo za branje'.<\/p>\n

Kaj pomeni 'nespremenljivost'<\/h2>\n

\nTermin 'nespremenljiv operacijski sistem' ozna\u010duje, da sta korenska in uporabni\u0161ka mapa name\u0161\u010deni v na\u010dinu 'samo za branje'. Vse spremenljive podatke pa shranjujemo v mapi \/var. Podoben pristop uporabljajo razvijalci ChromeOS<\/a><\/noindex> in macOS Catalina<\/a><\/noindex>. Tak\u0161en pristop pove\u010duje varnost operacijskega sistema in prepre\u010duje brisanje sistemskih datotek (na primer po pomoti).<\/p>\n

Eden od \u010dlanov Hacker News je v ustrezni temi je povedal<\/a><\/noindex>, da je neko\u010d po nesre\u010di izbrisal vrsto sistemskih datotek, ko je spreminjal temo Ubuntu Yaru. Pri tem mu ni ostalo varnostnih kopij zaradi napake v regexu. Po njegovih besedah bi nespremenljiv operacijski sistem pomagal prepre\u010diti te\u017eave.<\/p><\/blockquote>\n

\nNamestitev posodobitev je tudi poenostavljena \u2014 za to je dovolj, da ponovno za\u017eenete sistem z nove slike. Dodatno lahko hitro preklapljate med ve\u010d vejami (izdajami Fedor). Na primer, med trenutno razvijajo\u010do razli\u010dico Fedora Rawhide<\/a><\/noindex> i repozitorijem updates-testing<\/a><\/noindex> z na\u010drtovanimi posodobitvami.<\/p>\n

Kak\u0161ne so razlike od klasi\u010dne Fedor<\/h2>\n

\nZa namestitev osnovnega okolja (\/ in \/usr) se uporablja tehnologija OSTree. Lahko bi rekli, da gre za 'versioning' sistem RPM<\/a><\/noindex>-paketov. RPM-paket se v repozitorij OSTree prenese s pomo\u010djo rpm-ostree. Pri namestitvi paketa ustvarja<\/a><\/noindex> restore point that can be reverted to in case of failure.<\/p>\n

OSTree also omogu\u0107ava<\/a><\/noindex> installs applications from dnf\/yum repositories and repositories not supported by Fedora. For this, 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 with it.<\/p>\n

The mechanism used for updating applications is Flatpak<\/a><\/noindex>. It runs them in containers. A Flatpak package includes only those dependencies specific to the application. All base libraries (like GNOME and KDE libraries) remain connectable runtime environments. This approach allows for reducing package sizes by excluding duplicate components.<\/p>\n

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

To install applications that are not packaged in Flatpak, one 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 other distributions with tasks similar to Silverblue. An example could be MicroOS<\/a><\/noindex> from openSUSE. This 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-based applications that are not available in Flatpak format. The host system for running the containers is formed based on the official repository. openSUSE Tumbleweed<\/a><\/noindex>.<\/p>\n

MicroOS was developed for deployment in large-scale environments (for example, in data centers), but it can also work on individual machines.<\/p>\n

An example of another similar development could be NixOS<\/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 install the system and configure it manually. The state is described in a special file: it specifies all packages and authentication settings. Then, the package manager automatically brings the OS to the specified state.<\/p>\n

This system is actively uporabljajo<\/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 on corporate IaaS:<\/b><\/p>\n