Post by Bobbie Sellers Post by Bud Frede Post by Bobbie Sellers
I can see that there might be a need for such as
systemd in enterprise distributions like Red Hat but fail
to see any use for it in personal computing which is not
all I do but mostly.
I prefer systemd on my personal computers - or at least on those that
don't use launchd. :-)
I feel that systemd works well for both servers and for personal
computers. It works well on the various Raspberry Pi's that I have
running at home too.
The only thing that I'm running right now that doesn't use systemd or an
equivalent is my firewall, which runs on HardenedBSD.
And how does systemd contribute to your use of the computer?
I see that you use HardenedBSD so I doubt it contributes to your security.
It's far easier to use and more feature-rich than the hodge-podge of
init scripts we had before. Upstart had some good features, but I still
needed to use things like daemontools, god, or supervisord.
Here's an example of how systemd helps me:
I regularly work with an app that needs access to its data files when
starting up. It can use init scripts or systemd and not all environments
have switched to using systemd for this yet. (They're mission-critical
production environments, so the people that run them are very
conservative when it comes to making changes.)
Some of those environments use NFS for some of this app's data
files. With init scripts starting this app, the app will start up even
if there isn't any network connectivity. "Bad things happen" when it
starts up with missing data files.
Systemd prevents this by not letting the app start unless it has what it
needs. Dependencies have to be met before systemd will start the app.
Another example if that the mechanisms for controlling services are now
the same from distro to distro. In the past each distro had its own set
of init scripts, with different options, etc. It was a PITA to deal with
it all. I find it much easier to work with multiple distros now, and to
understand how they boot and manage services.
A lot of the peripherals we use today are hot-plug. We have high-speed
connections like USB available and don't have to permanently plug things
in to the motherboard as much as we used to. Our use of hardware is more
fluid, and systemd manages this far better than init scripts ever did.
As for security, it's now easier to manage services and understand how
my systems boot, so I'd say that security is improved with systemd.
My firewall running HardenedBSD doesn't necessarily say anything about
systemd or my use of it and Linux on various systems. Firewalls have
different requirements than a typical desktop or server. In addition,
there are some very good firewall packages that do use systemd. I just
happen to use one that runs on BSD.
The major drawback to systemd is that it requires us to learn something
new. In my case, I need to learn new things all the time anyway, and as
for systemd, I started putting my time in with it years ago, so it's not
The way I see systemd is that it's basically all upside and no real
downside at this point. Why wouldn't I want to use it?