sysvinit-2.89 has been on the to-do list for a while, but development has been at such a slow pace, it'll be quite a while if and when it arrives. They have a repository you can gran the sources from, but 2.88dsf is completely stable.

I don't know if someone has already posted a link to this funny strip:

http://www.commitstrip.com/wp-conten...alenglish3.jpg

2 members found this post helpful.

Nice.

Since this thread goes on the premise that Slackware WOULD be ditching the traditional BSD init for a more modern one assuming there is enough of a major gain in doing so I still find it highly unlikely that systemd would ever be considered by Pat because of the sheer intrusiveness that systemd is. I would probably guess that openRC might be a fairly good candidate. Also there is some benefit in the fact that systemd even exists, because that way other developers of other init systems will take cues from systemd of what NOT to do and be as minimally invasive to the system as possible and at the same time actually providing a noticeable improvement in startup as well as keeping complexity as close to a minimum as possible. All developers of alternative init systems are pretty much benefiting from systemd's existence already. Systemd is making all the blatant mistakes and breaking so much of Linux that they know which corners to turn and which paths to steer clear of, plus there is always more 'bleeding' edge distros such as fedora that will blindly use systemd anyways, so again let them be the guinea pigs.

My opinion or prediction, most likely might be that OpenRC might be a pretty good candidate for replacing the current init system, but again not without extensive testing as well as determining if there is any benefit at all in choosing a new 'wheel' , as well as determining if it needs to be replaced in the first place.

2 members found this post helpful.

Doesn't OpenRC more or less use sysvinit still in some way?