Systemd
Peale seda, kui Ubuntu Upstarti välja arendas, hakkasid mitmed distrod, sh Fedora ja openSuSE selle suunas liikuma. Nüüd on viimased kaks aga end ringi pööranud ja juba 12.1 openSuSE-s oli tegelikult initiks hoopis uus poiss nimega Systemd.
See on üks isevärki põnev tegelane ja üks blogiartikkel paljastab pisut telgitaguseid:
http://patrakov.blogspot.com/2011/01/writing-systemd-service-files.html
systemd ise oskab näiteks protsesse monitoorida ja neid taaskäivitada. Samuti pidada systemd-ga saama teha nii, et mõni protsess käivitub alles siis, kui mõni teine protsess üritab tema socketi külge ühenduda.
http://en.gentoo-wiki.com/wiki/Systemd
if you are a regular desktop or simple server user, it probably will work without you needing to do anything special (except using init=/usr/bin/systemd in your kernel command line and maybe needing to reemerge a couple of packages with USE="systemd"). If you use something more complicated (RAID, LVM, NFS, that kind of stuff), you probably will need to enable or perhaps change a couple of services, but that's it. If you use a not very common daemon, maybe you will need to write its service file; but it's ridiculous easy (specially when compared to sysvinit scripts).
Just a word of advice: if you are a normal laptop user, systemd has replaced most of the functionality of consolekit; so if you boot with systemd, several packages need to have enable the systemd USE flag (and the consolekit one disabled). In particular, pambase and polkit need to set either systemd or consolekit, but cannot set both.
