![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
SystemD is developed by Red Hat developers. RHEL is an OS created by te private company Red HAt that is currently in the hands of IBM. It is very large and consists of many parts that do many things.
"systemd is a software suite that provides an array of system components for Linux[7] operating systems. The main aim is to unify service configuration and behavior across Linux distributions.[8] Its primary component is a "system and service manager" — an init system used to bootstrap user space and manage user processes. It also provides replacements for various daemons and utilities, including device management, login management, network connection management, and event logging. The name systemd adheres to the Unix convention of naming daemons by appending the letter d.[9] It also plays on the term "System D", which refers to a person's ability to adapt quickly and improvise to solve problems.[10] "
Source: Wikipedia
"The Unix philosophy is documented by Doug McIlroy[1] in the Bell System Technical Journal from 1978:[2]
- Make each program do one thing well.
- To do a new job, build afresh rather than complicate old programs by adding new "features".
- Expect the output of every program to become the input to another, as yet unknown, program.
- Don't clutter output with extraneous information.
- Avoid stringently columnar or binary input formats. Don't insist on interactive input.
- Design and build software, even operating systems, to be tried early, ideally within weeks.
- Don't hesitate to throw away the clumsy parts and rebuild them.
- Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you've finished using them."
To me, the problem with SystemD is that it is too large and and does too many things. It seems to be an all or nothing story, taking away the freedom of devs to puzzle their OS together in their own way. The software becomes indispensable, and forces developers to adjust their software to it, in order to retain compatibility for their programs. Etc.
