Machinery supports inspection of SLES11 and SLES12 systems right now. It would be beneficial to be able to also inspect RHEL systems for various reasons:

The goal of my project is to achieve total world domination. == Hell, yeah!

<a href="http://trivialine.herokuapp.com/" target="blank"><img src="https://scontent-a.xx.fbcdn.net/hphotos-xap1/v/t1.0-9/103560303124060156120696822168581672115471n.png?oh=d7ff3f6c32934ea362156d071e0b660a&oe=54B1308C" width="460px"/></a>

We have the pleasure to introduce you to the first Online Multiplayer Trivia:

It's 1.5yrs since we've launched the last Studio version. Customers are asking about a roadmap, a new version... After discussions with AJ, Adrian, Alex, I want to create a draft plan/concept how such a Studio successor could look like.

Package a basic, stripped down version of sysvinit for emergency cases, so you can repair a failed system without interference. My goal is not to replace systemd with sysvinit again, but to provide a sysvinit-base package that does not have any dependencies at all and can just be installed on any system. sysvinit will only be used in exception situations by specifying the kernel parameter "init=/sbin/init" or something like that. The package will come with the binary, a minimal inittab and a basic boot script that does only the really needed stuff. Experiment with an extension to have sysvinit execve systemd, so people can boot into their allmighty uber-daemon once the system has been fixed.