140
Is Systemd that bad afterall?
(sopuli.xyz)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I guess I'm in the camp if it doing too much. I prefer each program has its own script to run in a more isolated manner from anything else the system does so if one program locks up everything else on the system runs independent from the other software that has stopped responding to system calls.
I partially agree. But on the other hand I like the convenience.
Example: I need to enable ntp client on a machine? Just enable and start the service and done!
You don't need systemd for that. It has always been the case before systemd even existed.
BSD does that without systemd.
I enjoy the seamless experience it offers. I doubt Linux in general could be noticeable faster with better optimized SystemD or with perfect init for speed.
Funnily enough a lack of isolation is exactly what I hated most about the init scripts. Particularly the lack of isolation from the caller's environment, user,...