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'm not aware of the politics in this, are they saying the systemd people are rude, or that they just refuse to make their code compatible?
They indent using four spaces, and also apply this indentation to the braces at the start of a function. Spaces! Four of them! Not tabs, spaces! And they indent their braces!
Removal from Busybox is too good for them, they should be exiled from the planet!
Oh, a framework.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
What is the point of converting an existing daemon to be started with systemd? Quite soon the systemd has assimilated the functionality of that daemon anyway..