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.
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.
"The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
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.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"