News for hackers. Stuff that matters.

A comment on Why Did It Take Devuan Two Years to Replace Systemd?. Parent comment

Re:Why Did It Take Devuan Two Years to Replace Systemd? by smhenderson on Tuesday July 11, 2017 @04:16PM (#14747645)
It's not systemd that's the problem, it's libsystemd0. Try removing it on Stretch. It's doable [0] but it's a pain and makes future maintenance fragile and error prone. And if I understand correctly once you do so you're not running Gnome on that system anymore...

[0] http://lkcl.net/reports/removing_systemd_from_debian/

[ Parent | on HN ]
Re:Why Did It Take Devuan Two Years to Replace Systemd? by bandrami on Tuesday July 11, 2017 @04:23PM (#14747713)
I don't run dbus, let alone Gnome. (getting X11 to work without dbus on Debian is also a pain, though also doable.)
[ Parent | on HN ]
Re:Why Did It Take Devuan Two Years to Replace Systemd? by catdog on Tuesday July 11, 2017 @04:34PM (#14747815)
Which is a purely religious problem as libsystemd0 basically does nothing if systemd is not running. Debian is a binary distribution, a lot of stuff is linked against libs you probably never use, that's just how it is.
[ Parent | on HN ]
Re:Why Did It Take Devuan Two Years to Replace Systemd? by smhenderson on Tuesday July 11, 2017 @04:47PM (#14747902)
I didn't say it was being used but the Devuan project wants it out of their distro and dependencies on it are much harder to resolve than dependencies on systemd bins.
[ Parent | on HN ]