Slashdot Mirror

← Back to Stories (view on slashdot.org)

Busybox Deletes Systemd Support

Posted by timothy on from the changed-our-minds dept.

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.

3 of 572 comments (clear)

  1. Awesome news by Anonymous Coward · · Score: 5, Interesting

    Great work BusyBox!

    Now if some of the desktop distros would listen to their core base and drop systemd as the default things would really be looking up for 2015 and next year.

    That's not to say some of the ideas in systemd are entirely without merit. But the execution is entirely and utterly wrong. Maybe not for a version of Windows, but totally wrong for UNIX.

  2. As I said before... by QuietLagoon · · Score: 3, Interesting

    I doubt if everyone who jumped aboard the systemd cargo ship really knew the journey they were in for. Some of those travelers started to regret their ticket purchase when sudo was eaten up by systemd. And others... well it will take a bit longer to realize their fate.

  3. The systemd way by medoc · · Score: 5, Interesting

    Just an anecdote: during a recent upgrade from Debian Wheezy to Jessie, the first boot into the new system failed with a message from systemd about mtab not being a link into /proc/something (a trivial problem as far as I can see).

    Can't remember the exact message from systemd, but it was something about being "frozen"

    No going into single user, nothing, just F... you and go reboot on the CD image. Happy enough that the machine was on my desk...

    And they wonder why many people don't like systemd....