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.
http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet
Below is also a FAQ on systemd
http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions
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.
http://0pointer.de/blog/projects/systemd.html
Wondering now when we are going to see this in RHEL and if and when systemVinit will be completely deprecated.
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.
Posted by: Elmo | January 31, 2012 at 21:10