Busybox Deletes Systemd Support

ewhac writes: On 22 October, in a very terse commit message, Busybox removed its support for the controversial 'systemd' system management framework. The commit was made by Denys Vlasenko, and passed unremarked on the Busybox mailing lists. Judging from the diffs, system log integration is the most obvious consequence of the change.

Comments

The message in question:

[Chewbacon]

"systemd people are not willing to play nice with the rest of the world. Therefore there is no reason for the rest of the world to cooperate with them."

Wonder why so many other devs are so eager to put the systemd dick in their mouths.

Re:Well, at least someone is willing to say it!

[Barsteward]

i bet you didn't like init scripts until you learnt how to code them by looking up and learning from a bash manual. There is nothing wrong with learning unless you feel you've reached your limit of learning new stuff.

Re: Dropping stderr and syslog messages...

[drinkypoo]

Look at where systemd originated, from someone that worked on a user-level sound daemon.

From someone who worked on a user-level sound daemon which became, for several years, the most problematic part of the linux desktop. You couldn't hardly search for anything Linux-related for years without finding people asking questions about how to fix their pulseaudio problems, offering advice for how to solve pulseaudio problems, trying to figure out how to rip pulseaudio out of their system so it stops using all their CPU, etc etc. Lennart Poettering couldn't code his way out of a nutsack.

Re: The Commit Message

[BitZtream]

The situation you described is an example of "Linux Admins" ... I.E random people who installed calling themselves admins and then your dumbass hired the clueless wastes.

Systemd does nothing to solve that problem in any way and you haven't provided a reason why it would.

You seem to be arguing that if YOU do everything then you don't have problems with other admins.

This a problem with you and your inability to manage or work with a team. In short, your just a clueless shitty admin that thinks this half assed method to obscure the system to the point that no one else wants to touch it is a good thing.

You're an idiot who doesn't understand what you're doing, there's no possible way you could understand why systemd is shit