-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

Linux Service Management Made Easy with systemd

If you've been in the computer world for any length of time, you may have seen that we geeks can get quite passionate about our operating systems. In the early 1990s, I finally replaced my text mode-only 8088 machine with one that could run a graphical interface. I first gave Windows 3.1 a try, and quickly decided that I really hated it. So, I bought a copy of OS/2, which I liked much better and ran for quite a few years on my home-built 486 machine. But, all of my geek buddies at work were big Windows fans, and they kept arguing with me about how much better Windows is. I thought that they were all crazy, and we kept getting into some rather heated arguments.
Then, when I got into Linux, I quickly learned that you don't want to go into any Linux forum and ask which Linux distro is the best for a newbie to start with. All that does is start fights, leaving the poor newbie more confused than ever. And now, the fight is over whether or not systemd
is a good thing. Here are some of the objections:
systemd
violates the Unix concept of having each utility just do one thing but having it do it well.journald
component saves system logs to a binary format, which some people believe is more easily corrupted than the plain-text files that rsyslog
creates.If you look at things objectively, you might see that the objections aren't so bad:
systemd
ecosystem includes more than just the init
system. It also includes network, bootloader, logging, and log-in components. But those components are all optional, and not all Linux distros use them in a default setup.systemd
were to be proprietary, the free code is still out there, and someone would fork it into a new free version.systemd
. But that's also true of OpenSSL, the Bash shell, and even the Linux kernel itself. To complain about systemd's
security would only be valid if the bugs hadn't gotten fixed.journald
component does create log files in a binary format. But it's still possible to run rsyslog
on systemd
distros, and most do. Some distros, such as the Red Hat Enterprise Linux 8 family, use journald
to gather system information and then just have journald
pass the information to rsyslog
in order to create normal text files. So, with RHEL 8, we have the best of both worlds.Soon after the release of systemd
, some people who had never even tried it put up blog posts that explained why systemd
was pure evil and that they would never use it. A few years ago, I created a systemd
tutorial playlist on my BeginLinux Guru channel on YouTube. The first video is called Why systemd?. Quite a few people left comments about why they would never use systemd
and said that they would change to either a non-systemd
Linux distro or to a FreeBSD-type distro in order to avoid it.
The bottom line is this: all enterprise-grade Linux distros now use systemd
. So, I think that it might be here to stay.