Note that I wasn&#x27;t suggesting that systemd is <i>itself</i> an attempt at an &quot;init daemon with branded zones&quot;—instead, it&#x27;s a particular runtime that will increasingly differentiate itself from POSIX Linux, and I believe that that <i>friction</i> will eventually cause developers to want to <i>create</i> an init daemon with branded zones to supercede systemd, where emulating systemd-as-it-stands (for apps built to expect it) would be one of that multi-runtime system&#x27;s goals. With the POSIX people and the bigcorp Linux providers pulling in opposite directions, a multi-runtime Linux would be the only Nash equilibrium. (Though it&#x27;d need someone like FreeDesktop to suggest it and start a working group for it, because neither &quot;side&quot; would care about it on their own.)<p>That may not be the way things play out, certainly. Things might just diverge and stay that way, if nobody cares enough to change things. But there are unknown unknowns that can give things a very hard shove in that direction. For example: imagine that systemd decides to integrate deeply with GNOME, to the point that you now have an integrated &quot;systemd+glib+GNOME platform&quot; with a unified API, the way that OSX is a &quot;launchd+CoreFoundation+Cocoa platform&quot;. <i>That</i> would be an extremely divergent target in the Linux ecosystem introducing a lot of friction to everyone else&#x27;s development efforts—similar to the early stages of the Android project—and it would get a lot of people&#x27;s hackles up. But it&#x27;s not out of the realm of possibility for RedHat and Debian to agree on something like that.