Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
en:philosophy:systemd_denial [2022/03/24 13:22] i3_relativism add references from old news post |
en:philosophy:systemd_denial [2022/11/18 12:35] throgh [Points for criticism in detail] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | future page for init freedom article | + | ====== systemd: Denial or just alternative ways? ====== |
- | maybe use already installed sync plugin | + | We are surely aware about the criticism towards systemd as project. But this article should not only be focussed onto that and be therefore more oriented towards our reasoning for a system beyond using only bloated packages and frameworks. So we could now list for sure many reasons why we stay critical towards the adaption for systemd as basic init-framework, |
- | As systemd doesn' | + | ===== Introduction ===== |
- | To ease the transition, | + | systemd |
- | Further details: | + | As Hyperbola is created as pure lightweight system the orientation of systemd is not following the [[:social_contract|Social Contract]] to **respect modular and lightweight design**. This was announced within 2017 in a dedicated [[https:// |
- | | + | With the essential design-decision being just more than only init and management systemd has also included more attack surfaces and further security-issues. To be mentioned there are dereferencing null pointers ([[https:// |
- | Mount efivarfs read-only (https:// | + | |
- | | + | ===== Back and forth: The role of init-systems ===== |
- | | + | |
- | | + | There are different approaches followed by the different systems and distributions. Nevertheless the key-role of an init-system is just to start the basic system and initialize the services. Afterwards it is about a supervisor to look behind the services running and removing those crashed ([[https:// |
- | | + | |
- | | + | Again the size and the understanding of systemd in a whole is here the major point for issues: Too many components integrated, too many design-flaws within and too less transparency. Hyperbola has chosen for a reason to follow strict the [[en: |
- | | + | |
- | | + | ===== Points for criticism in detail ===== |
- | | + | |
- | | + | We will never address criticism making usage of personal attacks as we conclude neither being unfair nor using false argumentation methods. Besides there are many points to be found making it further a problem to use systemd for any system with lightweight focus. |
- | | + | |
- | systemd-resolved DNS cache poisoning (https://seclists.org/oss-sec/ | + | === Breaking promises and immaturity === |
+ | |||
+ | “After udev is merged into the systemd tree you can still build it for usage outside of systemd systems, and we will support these builds officially. In fact, we will be supporting this for a long time” | ||
+ | http:// | ||
+ | |||
+ | ”…this will effectively also mean that we will not support non-systemd systems with udev anymore starting at that point. ' | ||
+ | http:// | ||
+ | |||
+ | “kdbus support is no longer compile-time optional … We encourage all downstream distributions to begin testing kdbus by adding it to the kernel images in the development distributions, | ||
+ | http:// | ||
+ | |||
+ | === Stability promises failed === | ||
+ | |||
+ | " | ||
+ | http:// | ||
+ | |||
+ | < | ||
+ | |||
+ | === Scope of the project === | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | === Problematic bugs and responses === | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[https://lists.debian.org/ | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https://www.agwa.name/ | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https://github.com/systemd/systemd/issues/6237|systemd can't handle the process | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | === Conceptional problems === | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | ===== Conclusion for the Hyperbola-project ===== | ||
+ | |||
+ | With the retrospective of all the points listed here Hyperbola has the stance not to accept | ||
+ | |||
+ | So systemd has to persist the comparison towards other possible init-systems and in that way is for sure too big, too complex and full with flaws we don't want to accept as we would therefore need to be worried even on top of continuous upgrades for just one essential part. And even though every single point can be declared as solved or in some way older, we just don't want to use systemd as single-point for a failure as it just this simple. |