Systemd/Systemctl in Fedora 15 — WTF is this?

Nausea_smiley Fresh install of Fedora 15 on my home machine… feeling great, running great. Got myself a fast new SSD, and upgraded to a new quad core and 8gb of ram. Then i run into this.

[root@fedora15 ~]# service nscd start
Starting nscd (via systemctl):                             [  OK  ]


Oh man whats this — systemctl. If this is anything like upstart I am going to be ill.  Well guess what, it is. Even worse, its also kinda like svcadm in Solaris10.

"systemd is a replacement for the System V init daemon for Linux. It is intended to provide a better framework for expressing services' dependencies, allow more work to be done in parallel at system startup, and to reduce shell overhead"

Seriously, was there something wrong with systemV init scripts that i was not aware of.  Looks like systemd is enabled by default in Fedora15,

Anway, the link directly below will take you to a nice cheatsheet for systemd commands. Looks like they are also mucking around with the sysivinit Runlevels. Scroll down for that little gem.

Below is also a FAQ on systemd

And a bit more insight into what it is and where it comes from

Finally the blog post from the developer announcing systemd. Apparently from last year.

Wondering now when we are going to see this in RHEL and if and when systemVinit will be completely deprecated.

2 thoughts on “Systemd/Systemctl in Fedora 15 — WTF is this?

  1. Totally agree on “WTF is this”. If upstart couldn’t get worse… well it has, and to upstart’s credit it’s something new and completely different. (i.e.:
    $ sudo systemctl setup vboxdrv
    I’m sorry dave…
    $ sudo systemctl setup vboxdrv.service
    I still don’t know what you speak of
    $ sudo /etc/init.d/vboxdrv setup
    … )
    Yeah, if you want to gain a couple of seconds on boot time with parallelism … it’s not worth it. Five second boot time, OK, will concede.

  2. Its an utterly disgusting convoluted mess.
    There’s no reason existing facilities couldn’t have been upgraded in a backwards-compatible, phase-able and organized manner. I guess that would have required imagination and some understanding of why things are the way they are, in place of subjective egocentric over-engineering.
    Steps like this are morphing Linux into something else, that at some point should no longer be referred to as Linux. Mainstream distributions like Debian should be more careful about absorbing such influences emanating from the corporate world of development.
    I read that systemd was made originally as a “hobby project” by one of the developers who worked on “Pulse Audio” – says it all.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.