Personal choice... (Score: 2, Interesting) by email@example.com on 2015-07-29 19:23 (#FV3Z) For ME, I don't like the way that systemd is marketed as a "sysVinit replacement", but systemd has hooks into all sorts of things, including (but certainly not limited to) system logging and GUI applications.If sysVinit is going to be replaced, let it be replaced by an actual init system, not something that has more in common with mold, getting its tendrils into everything imaginable.That is, admittedly, a personal opinion. I'm currently running Devuan on a netbook and I'm quite happy with it. Would I *use* another distro? Sure, if I had to. If I have a choice though... Re: Personal choice... (Score: 1) by firstname.lastname@example.org on 2015-07-29 20:08 (#FV81) While a reasonable point, you certainly can't claim Linux was sleek and simple and clean before systemd. For many years there has been a huge mess with ConsoleKit, NetworkManager, avahi, dbus, dcop, hal, pam.d, udev, devfsd, sysfs, +proc, devtmpfs, kudzu, zeroconf, and much more crud. It seems to me that when USB came along and make extreme plug-and-play user-facing, Linux distros just kept throwing in everything but the kitchen sink to make each scenario work right for ignorant desktop users and GUI management tools (and a nightmare to configure and debug for administrators). With systemd starting to take over bits of some of those, I'm hoping for a bright future where there's one little simple place where such device configuration can be done (and those being the same across distros, and also not changing between each major release), and not several that do different but partially-overlapping bits of the puzzle, as we have to tolerate now. Maybe systemd is not actually be the best answer to that problem, certainly the BSDs manage to work fine without the Linux insanity I listed above, but at least it is finally some progress towards unification and simplification of the complete mess.