3 ms·
> or can't ship Gnome because of GDM's dependency on Systemd Void Linux is using GDM with elogind and seems fine: https://github.com/void-linux/void-packages/b
by m45t3r 7y ago
> or can't ship Gnome because of GDM's dependency on Systemd
Void Linux is using GDM with elogind and seems fine:
https://github.com/void-linux/void-packages/blob/master/srcpkgs/gdm/template https://github.com/void-linux/void-packages/blob/master/srcp...
> even the Linux kernel with a BSD one
You know, Debian GNU/kFreeBSD is as most a fork of Debian as Devuan. They share most of the packages definitions, however some core parts (like the init scripts) are _very_ different.
> but you can't replace the init system, even though several alternatives exist
Well, you can. It is just that Debian maintainers don't want to maintain this complexity in their own system. Supporting only one init system is already difficult, imagine supporting N init systems like you're suggesting (and this includes bug reports: do you really think that this is a good usage of the time from maintainers to support that niche init system with 3 users?).
However there is nothing impeding you to use your own Debian installation with any init system you want. Or even better: switch to Devuan.
- the_why_of_y 7y ago> It is just that Debian maintainers don't want to maintain this complexity in their own system Sigh... don't believe the FUD, there's a standing Debian Technical Committee decision [1] that multiple init systems must be supported, it's just that the Devuan people don't want to work on a distro that includes a systemd source package in its archive, so instead of maintaining the sysvinit scripts in the Debian archive they went off forking. [1] https://lists.debian.org/debian-devel-announce/2014/08/msg00001.html https://lists.debian.org/debian-devel-announce/2014/08/msg00...
- m45t3r 7y agoTIL. So it is even easier and I don't know what's the problem with dvfjsdhgfv. I think unless Debian stopped adopting systemd nobody would be happy.