Slashdot Mirror
Debian Votes Against Mandating Non-systemd Compatibility
paskie writes: Voting on a Debian General Resolution that would require packagers to maintain support even for systems not running systemd ended tonight with the resolution failing to gather enough support.
This means that some Debian packages could require users to run systemd on their systems in theory — however, in practice Debian still works fine without systemd (even with e.g. GNOME) and this will certainly stay the case at least for the next stable release Jessie.
However, the controversial general resolution proposed late in the development cycle opened many wounds in the community, prompting some prominent developers to resign or leave altogether, stirring strong emotions — not due to adoption of systemd per se, but because of the emotional burn-out and shortcomings in the decision processes apparent in the wake of the systemd controversy.
Nevertheless, work on the next stable release is well underway and some developers are already trying to mend the community and soothe the wounds.
This means that some Debian packages could require users to run systemd on their systems in theory — however, in practice Debian still works fine without systemd (even with e.g. GNOME) and this will certainly stay the case at least for the next stable release Jessie.
However, the controversial general resolution proposed late in the development cycle opened many wounds in the community, prompting some prominent developers to resign or leave altogether, stirring strong emotions — not due to adoption of systemd per se, but because of the emotional burn-out and shortcomings in the decision processes apparent in the wake of the systemd controversy.
Nevertheless, work on the next stable release is well underway and some developers are already trying to mend the community and soothe the wounds.
This is the same community that you can still start a street fight, or at least a troll war, by asking "Which is better: emacs or vi?" I'm not sure they're ever going to get over this. But, like the above question, the world will move on and leave them behind.
"Be particularly skeptical when presented with evidence confirming what you already believe." -
Tell me why any of that is necessary? It's exactly like how Windows manages network interfaces.
Don't worry - systemd will handle that for you, and bring your interfaces up whether you want them up or not, using hundreds of sensible MSDOS .ini files. And if you run into problems, you can always check the systemd-journald binary logs through a suitable systemd secret decoder program. Unless, of course, the system went down before the non-transactional logging went to disk.
Rubbish. FreeBSD is insecure crap. You should be using OpenBSD.
OpenBSD is run by that thug Theo, you should try NetBSD.
What a jerk - only a loser would use NetBSD, it's DragonFly or nothing.
Watch this Heartland Institute video
Soon, all linux distros will contain 3 files: /boot/image-blah /vmlinuz /sbin/systemd
You won't need anything else!