{"id":114150,"date":"2024-03-06T12:25:51","date_gmt":"2024-03-06T10:25:52","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/proekt-postmarketos-predstavil-sborki-na-baze-systemd"},"modified":"2024-03-06T12:25:51","modified_gmt":"2024-03-06T10:25:52","slug":"proekt-postmarketos-predstavil-sborki-na-baze-systemd","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/proekt-postmarketos-predstavil-sborki-na-baze-systemd","title":{"rendered":"The postmarketOS project has introduced builds based on systemd.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The developers of the postmarketOS project, which is developing a Linux distribution for smartphones based on the Alpine Linux package base, the standard C library Musl, and a set of BusyBox utilities, announced the provision of support for the system manager systemd. As a result of work to implement systemd support, which lasted about a year, a prototype build has been prepared and is available for testing, in which systemd is used instead of the OpenRC initialization system. <\/p>\n
Support for creating builds based on OpenRC will be maintained for at least as long as this system is used in Alpine Linux. When building postmarketOS images, the option to choose OpenRC in pmbootstrap remains. Among other things, OpenRC is planned to continue being used by developers of the graphical shell build Sxmo (Simple X Mobile), which is based on the Sway compositing manager. <\/p>\n
Builds with systemd will continue to be formed on the Alpine Linux package base, despite the fact that this distribution does not support systemd and uses the Musl C library. Systemd officially supports only the Glibc C library, and postmarketOS developers have to use additional patches, which they plan to integrate into the main body of systemd over time (work is being done with systemd developers to simplify integration). <\/p>\n
The reason for implementing support for systemd is cited as the complexity of maintaining the OpenRC-based initialization stack amidst the ever-growing dependencies of GNOME and KDE on systemd components. To ensure the functionality of GNOME and KDE tied to systemd, various wrappers had to be used, and the price of operating without systemd was the necessity of maintaining these wrappers in proper condition and synchronizing with the development of GNOME and KDE, in conditions where certain necessary functions were missing in the wrappers, as well as the unpredictability of their continued maintenance by developers. <\/p>\n
For compatibility with the hostnamed, localed, and timedated services, the openrc-settingsd layer was used; the eudev package was implemented instead of udev; elogind was used in place of logind; logbookd replaced journald; superd was utilized to ensure the functionality of systemd --user; and waked served as a substitute for systemd.timer.
<\/center> <\/p>\n
Among the layers used, proper support and the level of support for the necessary functionality are provided only in openrc-settingsd and eudev. The projects elogind, logbookd, and superd continue to be maintained but require enhancements, as they lack some necessary features, while waked has been without support for about a year. Additionally, the KDE Plasma Mobile developers would like to use the systemd-coredumpd service to simplify debugging, but its replacement, corecollector, has been unsupported since 2020. <\/p>\n
Regarding the necessity of using these services, the D-Bus APIs provided by hostnamed, localed, and timedated are employed in GNOME for changing locales, system settings, and time zones; udev is essential for managing connected devices; logind, systemd --user, and journald are used for managing user sessions in gnome-session; and systemd.timer is utilized in GNOME Clock. <\/p>\n
Among the new features that can be implemented in builds based on systemd are granular privilege management, the engagement of enhanced capabilities for security and service dependency management, full integration with cgroups, the use of socket activation (for instance, CUPS can only be started upon accessing the network port), and the availability of built-in tools for analyzing the boot process. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![\"The](\"\/wp-content\/uploads\/2024\/03\/958cea9cab0605fb126a29342b664518.png\")
<\/center> <\/p>\n