I blocked the install of systemd way back. Recently I tried to upgrade postgres+postgis. Turned out that postgis had a dependency on a package with had a dependency on a package which had a dependency on another package which had a dependency on systemd.
So I tried compiling it myself. One of te build dependencies had a dependency on a package which had a dependency on a package which, you guessed it, had a dependency on systemd.
I finally gave up and moved the database over to a jail on my freebsd box.
(The whole systemd tempest in the tiniest, most awkward of teacups never made a lick of sense to me--in no small part because, like 99% of people, the only time I ever interact with it is when I throw a service declaration out there, and Noah Kantrowitz's fantastic `poise-service` Chef cookbook abstracts that away for me.)
I have been informed today that a new MySQL cluster built at work on CentOS 7.3 doesn't reliably start MySQL on boot.
We have none of these problems with our FreeBSD servers. systemd eats away at my time every week and I loathe it. It might not be a nuisance for endusers but it's a nightmare for sysadmins.
Many times this.
At this point systemd is a whole lot more than an init system. Most people don't have a complaint with regards to systemd units or how fast it boots, it's more to do with the amount of dependencies it seems to be sucking in (at least from my experience).
So they do nothing as udev and systemd already are separate packages in Debian?
"Separate packages" does not imply "no dependencies".
Hint: udev in Devuan is just the unmodified Debian package. So much for the "heavy lifting" done by Devuan in the last years.
And udev w/o systemd is still supported upstream, just not building only udev (one also builds the systemd binaries and throws them away).
So, one person tried to write a replacement for udev and gave up. What should that tell me?
so yeah, there is practically no way to escape from systemd in Debian using vanilla packages.
Edits: I should review before posting.
Whether Devuan works better than Debian with the usual systemd removal remains to be seen, of course.
The whole it-is-a-binary-choice-between-systemd-and-system-5-rc idea is bunkum, a myth. It wasn't true on Debian, where the hoo-hah had votes amongst upstart, OpenRC, systemd, and System 5 rc. It wasn't true on Ubuntu and Fedora, which had both been using upstart for years before their respective switches to systemd. It isn't true on Devuan, per what is right in front of you stated by the Devuan people theirselves. It is discussed amongst several other myths at http://uselessd.darknedgy.net/ProSystemdAntiSystemd/ . You are propounding it.
If GP were "selfish" he wouldn't give a rat's arse about sysvinit in the first place, but in this community you clearly don't know the first thing about, there is such a thing as compatibility-friendly development. If a config you don't like is popular, you still end up having to support it; that is why all the popular python projects I wrote are still Python 2 compatible. If I wanted to have it my way, it'd all be Py3.6 only.
That, and systemd having large scope creep, absurd ways of dealing with bugs ("this old system is broken because it does not use our interface"), and generally behaving in a dominating and lock-in-promoting manner.
I found this list on the way: http://without-systemd.org/wiki/index.php/Arguments_against_...
(By the way, the mis-spelling "SystemD" has become a shibboleth over those years. Spell the name properly, lest you find yourself lumped in with the pot-stirrers and provocateurs by the rest of the world.)
There was a whole hoo-hah in Debian over what to replace System 5 rc with: upstart, OpenRC, systemd, or something else. It got raised to the Technical Committee, sparked several resignations, went to a vote of the entire Debian Developer membership, and lasted for a long time.
Contrast Debian with Arch:
It seems only x64 at first.
Devuan will do okay. Simple and stable distros will always have loyal users.