Μπορεί κάποιος να εξηγήσει το systemd controversy με σχετικά απλά λόγια; Γιατί από το link του αρχικού post δεν κατάλαβα απολύτως τίποτα.
The design of systemd has ignited controversy within the
free-software community.
Patrick Volkerding, the project lead of Slackware Linux, invoked this design principle in a criticism of the systemd architecture, stating that, "attempting to control services, sockets, devices, mounts, etc., all within one daemon flies in the face of the Unix concept of doing one thing and doing it well
1) Critics regard systemd as overly complex and suffering from continued
feature creep*, arguing that its architecture violates the
Unix philosophy*
2) There is also concern that it forms a system of interlocked dependencies, thereby giving distribution maintainers little choice but to adopt systemd (εκβιασμός)
3) The additional functionality added by systemd can be provided elsewhere and unnecessarily increases the complexity and attack surface of PID 1*. PID 1 should only be responsible for starting the rest of the init system and reaping zombie processes. The additional functionality added by systemd can be provided elsewhere and unnecessarily increases the complexity and attack surface of PID 1
4) The criticism also characterizes the architecture of systemd as similar to that of svchost.exe, a critical system component in Microsoft Windows with a broad functional scope
5) Critics have expressed their opinion that the dispute over systemd's centralized design philosophy, more than technical concerns, indicates a dangerous general trend toward uniformizing the Linux ecosystem, alienating and marginalizing parts of the open-source community, and leaving little room for alternative projects.
Επίσης υπάρχει τρελό μίσος για τον τύπο που έφτιαξε το systemd, τον ποτερινγκ
==========Τεχνικές διευκρινίσεις=======
*Feature creep is the excessive ongoing expansion or addition of new features in a product, these extra features go beyond the basic function of the product and can result in
software bloat and over-complication
*Unix philosophy have always been expected to follow the concept of DOTADIW, or "Do One Thing And Do It Well."
*As for PID1, the important point to understand is that in Unix-like systems, including Linux, every process except one is created by another process invoking the fork() system call. The one that isn’t created this way, is conventionally called init .
As init occupies the first slot in the kernel’s process table, its PID (process identifier) is 1.
It never dies (meaning ”if it dies then something Really Bad has happened”) but can re-execute itself, e.g. to change system state (or “run-level” as it’s traditionally called). It also acts as the reaper for dead processes, but we don’t need to go into that. (Είναι η κυρίαρχη διεργασία που κάνει κουμάντο στο σύστημα)
techrights.org
