Systemd, ten years later: a historical and technical retrospective

Re:Systemd, ten years later: a historical and technical retr... by kelnos on Monday May 04, 2020 @03:51AM (#23065521)

I still don't entirely get the point of Devuan. I put Debian buster on a low-RAM embedded box, and since systemd eats up precious RAM I'd rather keep, I just switched to OpenRC with

    apt install openrc && apt purge systemd

If I needed it, Debian packages elogind as well.

Rebooted and it worked perfectly. Now, I get that Debian doesn't really support OpenRC[0] (or sysvinit), and it could break in horrible ways when bullseye goes stable, or get removed entirely, but... I don't see why we need a fork before that happens? It seems like it's a lot of work to maintain a distro fork, when I feel like that effort could be more productively redirected to stronger maintenance and advocacy of OpenRC and/or sysvinit in Debian itself?

[0] Debian's openrc package hasn't been updated in a little over a year, which is indeed concerning. sysvinit does seem to be more actively maintained, though.

[ Parent | on HN ]

Re:Systemd, ten years later: a historical and technical retr... by wrycoder on Monday May 04, 2020 @07:16PM (#23074495)

Late reply, sorry.

The problem isn't systemd's init. It's probably fine.

The problem is the systemd project is taking over the userspace with mutually cross-linked modules.

Devuan was started by a group of Debian maintainers who disagreed with the direction systemd was taking Debian.

[ Parent | on HN ]