Ubuntu To Abandon Upstart, Switch To Systemd

[AJSB]

Sorry to so many Linux distros jumping the shark and selling their souls. At least Gentoo and Slackware have not gone bat shit insane and are not making their init systems garbage.

Amen to that !!!

[mendieta]

Thank you, Mark. This is a big "F yourselves kids" to people who systematically attack him and Canonical for everything they do. Sure, some of their decisions have been questionable, but also applies to me and what I do, and my wife still loves me

[prodigy_]

Bullshit. Give me one reason why migrating away from systemd would be any harder than migrating to it.

Sure. Actually there's exactly one reason reason for that: systemd is steadily becoming a dependency for everything else. When it is and when Red Hat starts charging everyone for it, we'll talk about how easy is to break out of a walled garden.

[TheBlackCat]

Sysvinit was a concise and non-intrusive daemon that only did what it was supposed to do and never interfered with anything else. Hence migrating from sysvinit to systemd is very easy but migrating from systemd to anything (!) else may be hard to impossible.

No, the replacement would just need a systemD compatibility layer, just like systemD and Upstart provide a sysV compatibility layer, and just like Wayland provides and X11 compatibility layer.

[johnc]

Implicit in this is that they're going to be dropping Mir soon too for all the same reasons.

[finalzone]

Forced is the key word here. But the the crowd seems to be gleefully cheering about their newfound chains. So maybe we should leave them to their celebration and just wait till hangover changes the mood?

systemd was chosen by majority of distributions and industries to get rid the legacy scripts burden.
Unhappy about the decision? build your own distribution with your favorite init and good luck maintaining it.
It seems the age of core fragmentation is coming to the end which is a good think for Linux itself.

[prodigy_]

No, the replacement would just need a systemD compatibility layer, just like systemD and Upstart provide a sysV compatibility layer, and just like Wayland provides and X11 compatibility layer.

Oh, so you can switch from X to Wayland today and everything that requires X will magically work?

[computerquip]

Sure. Actually there's exactly one reason reason for that: systemd is steadily becoming a dependency for everything else. When it is and when Red Hat starts charging everyone for it, we'll talk about how easy is to break out of a walled garden.

Most software that use systemd only optionally use it at compile-time. Most can use it dynamically based on its presence or just require systemd start a service for them.

RHEL 7 uses systemd...

[Scimmia]

Sure. Actually there's exactly one reason reason for that: systemd is steadily becoming a dependency for everything else.

Wrong. They're depending on some APIs which systemd defines, but can be implemented anywhere. Not only that, software is being rewritten to use those APIs, it would be the same when the software was rewritten to use the APIs for whatever is next. No difference between to and away there. Next.

When it is and when Red Hat starts charging everyone for it, we'll talk about how easy is to break out of a walled garden.

And you're basing this conspiracy theory on....what?

[computerquip]

Oh, so you can switch from X to Wayland today and everything that requires X will magically work?

If you have the XWayland plugin available, yes. It will spawn an X server whenever you attempt to start an X application and work just like an X application.