Why Did ArchLinux Embrace Systemd? (2016)

Re:Why Did ArchLinux Embrace Systemd? (2016) by megous on Monday October 21, 2019 @12:48PM (#21314390)

I'd like something like systemd, but with all high-level internals written in a embedded scripting language.

[ Parent | on HN ]

Re:Why Did ArchLinux Embrace Systemd? (2016) by bitwize on Monday October 21, 2019 @01:21PM (#21314810)

Might want to look into GNU Shepherd. The whole thing is written in Scheme.

[ Parent | on HN ]

Re:Why Did ArchLinux Embrace Systemd? (2016) by megous on Monday October 21, 2019 @01:39PM (#21315008)

It seems to have a very limited scope of just managing services. I sort of like that systemd is more tightly integrated with Linux and for example listens on netlink for network changes, or device hotplug events, or on input events for (power) button events, and allows to reconfigure the system based on changes dynamically, etc.

[ Parent | on HN ]

Re:Why Did ArchLinux Embrace Systemd? (2016) by michaelmrose on Monday October 21, 2019 @02:08PM (#21315346)

Maybe someone should extend shepherd.

[ Parent | on HN ]

Re:Why Did ArchLinux Embrace Systemd? (2016) by rurban on Monday October 21, 2019 @05:15PM (#21317455)

init.d was nice, using shell scripts. readable, editable, clean, extendable. I liked that

[ Parent | on HN ]

Re:Why Did ArchLinux Embrace Systemd? (2016) by genghizkhan on Monday October 21, 2019 @11:11PM (#21320048)

Just not maintainable, which is why distros switched away.

[ Parent | on HN ]