News for hackers. Stuff that matters.
Re:Obstacles for kdbus by bandrami on Friday April 24, 2015 @02:37AM (#9431744)
I have stayed away from the systemd hatred - is it still a huge issue?

Not for me, I use Slackware and don't want dbus or a QR code generator linked in to my init system.

I think the misadventures of udev set a whole lot of people off to start looking for every possible conspiracy theory they could find. Personally, I don't "hate" systemd; it's a probably-interesting solution to problems I just don't have.

Re:Obstacles for kdbus by digi_owl on Friday April 24, 2015 @01:03PM (#9434582)
The "major" issue is the tighter and tighter coupling between init and desktop login thanks to systemd-logind+"bunch of Freedesktop.org kits"+gnome (and with Wayland +KDE).

Eventually you have to go back to using FVWM for your GUI needs if you don't want to do a wholesale userspace-ectomy on a perfectly functional distro.

Never mind avoiding anything GTK or Qt based, as they are likely to depend on some lib form Gnome or KDE that in turn depend on something tied to the hip of systemd.

Seriously people, logind is at present in charge of handling the likes of laptop lid closure. If that does not bring out the WTFs, i dunno what will.

Re:Obstacles for kdbus by bandrami on Friday April 24, 2015 @01:32PM (#9434779)
Seriously people, logind is at present in charge of handling the likes of laptop lid closure.

It's sure as hell not for me; I still have never booted with systemd. If people choose a distribution in which it does, I wish them luck with that. It probably does solve multiple problems; like I keep saying they are just problems I don't have.

Re:Obstacles for kdbus by bitwize on Monday April 27, 2015 @05:02AM (#9445086)
The point is that even if you haven't booted with systemd -- you will. Tge desktop and GUI software of the future will depend on the integration it provides.