I just pin systemd to not be infected by random beta crap imposed by a misguided political decision, and if you care to read the previous comment, someone said it largely build most of the debs themselves, and they do not have the luxury to upgrade anymore. Do not try to read more into what others post, and peruse the thread when in doubt.

First time I tested it, 1.5 years ago, systemd was not a welcome upgrade. And besides, it may very well be the default init system, however installing it in a production servers when there are no dependencies (no Gnome for instance) is just breaking things for the sake of breaking them. This is the first time, it would be thoughtful to be a transition time. Ha, and this also breaks modsecurity, I forgot.

Fuck the voting/democracy shit. It is outrageous that without previous planning/package pinning all the systems get automatically upgraded to systemd without further asking. A true democracy would be to ask when installing "do you go with systemd or the alternative" and the sending the stats back to debian.

Read my post. You can pin systemd to -1. At the moment, I am largely based in Debian, I am just building 6 debs.

filter the threshold to 2 points and read my thread above.

If you do not understand the concept of open source, force by the numbers and respect, you may very well go to hell. Debian has arrived where it has today because of people. FreeBSD knows better than using that shit. Know that also trivago turned me down a year ago because my *BSD was a little rusty, They just said very vaguely "all of we are linux guys, and we thought we were more up-to-date with your FreeBSD stuff as we want to migrate there. Take your conclusions, if you are too busy insulting people and making up stuff.

Being "democratic" does make it better.

People be aware of some caveats upgrading. Been testing it in the last year, and using it since news year eve in less critical systems in production. systemd has to be pinned to -1 or your servers will get upgraded to it without any interaction from your part. Beware also that Apache configurations change. Some configurations might get broken. libjpeg8 was missing and docker.io still is; backports may solve this. Apache configurations changed a lot. Be also aware that things get installed by default, for instance I had to delete rpcbind from most of my servers. Be also aware open vmtools gets a little confused after the upgrade and needs to be upgraded explicitly.

A "fork" is some project picked up by others.

So Microsoft believes a shitty product will get better acceptance by the consumer changing the skin and the name. Interesting.

I remember vaguely some ISP doing this and it was told by the court to stop.

i guess there are many lunatics of a "minority" then out there. And it is not a lie. As for technical reasons given the Debian insistence in stable and true and tried packets, is still quite a mystery how systemd was used as the default so soon.

Interesting. i am using a highly customised, very lean Debian 8. I block/uninstall everything I dont need, including kernel modules. Might start making my own package of the kernel once kernel 4.1 comes out. As for systemd, I have pinned it and some other "niceties" to -1, no "turning up" by accident.

Ditto, that is why I have Linux server farms at work, and Apple stuff at home. And even then, often in a while ;)

You could always pray to the sysadmin god. Or find an use to a novel concept, a firewall.