SoylentNews is people
SoylentNews
Michael Biebl, long-time maintainer of systemd for Debian (2010 or earlier, based on changelog.Debian.gz), is taking undetermined holidays from packaging it. The e-mail was short:
Will stop maintaining systemd in debian for a while.
What's going on is just too stupid/crazy.
This takes place after he discussed a bug in which he expected systemd to respect local settings, and not rename network devices:
@yuwata a default policy like /lib/systemd/network/99-default.link should never trump explicit user configuration.
Later he seems surprised about how things roll there:
I'm amazed that I have to point this out....
The issue is locked currently, and also archived just in case, so everyone can read the initial report and the replies he got.
Opinion: It seems distribution developers are starting to get the stick too, not just users with their "errors" (taken from a reply). Will distributions finally wake up or is that they don't still grok the attitude of projects like this? [Or is it something else? --Ed.]
(Score: 4, Interesting) by ilsa on Monday January 21 2019, @08:49PM (6 children)
While I personally haven't run into any of the systemd issues that other people have reported, I can respect the current outcry of systemd being a sprawling mess that sticks its fingers in things it has no business too.
The thing is, the old init system is crap. Large swaths of quasi-system level annotated bash scripts is not rigorous, ugly and is a hassle to deal with. Especially when everyone has a different idea of how to manage their apps processes.
So what are the alternatives to systemd and why aren't they getting more attention? What happened to upstart, for example? Surely there are projects out there that do what systemd _should_ be doing without all the overreach?
(Score: 0) by Anonymous Coward on Monday January 21 2019, @09:39PM
Upstart lost most of its momentum when Ubuntu switched to systemd, but it still exists. Gentoo has OpenRC, which is like sysVinit but with much less cruft. There are only so many choices in the init system department. I think there are one or two other systems that are not widely used.
(Score: 0) by Anonymous Coward on Monday January 21 2019, @09:43PM (1 child)
Scripts can be improved:
### BEGIN INIT INFO
# Provides: lvm2-lvmpolld
# Required-Start: $local_fs
# Required-Stop: $local_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: LVM2 poll daemon
### END INIT INFO
DESC="LVM2 poll daemon"
DAEMON=/sbin/lvmpolld
DAEMON_ARGS="-t 60"
PIDFILE=/run/lvmpolld.pid
do_start_prepare() {
mkdir -m 0700 -p /run/lvm
}
This is mostly declarative. Only cmd is for special thing, that would need to be handled by separate scripts or forcing the daemon to do what init system wants, instead of the other way arround. It also boots in parallel, and the order is known ahead of time.
(Score: 2) by ilsa on Wednesday January 23 2019, @08:35PM
You've completely missed my point. IMO we shouldn't be using scripts at all to manage all the init stuff. Using scripts is sloppy, cumbersome and error prone.
The way systemd handles services/daemons in a declarative way is a far superior way to handle it because you don't have to rely on the script writer to do the correct thing, not run their process as root, etc.
Systemd would have been perfect if they had only quit while they were ahead and not turned it into the giant tentacled mess that it has become.
(Score: 2) by wirelessduck on Monday January 21 2019, @11:56PM
http://smarden.org/runit/ [smarden.org]
https://skarnet.org/software/s6/ [skarnet.org]
(Score: 0) by Anonymous Coward on Tuesday January 22 2019, @09:10AM (1 child)
I've run into a couple. It's pissed me off enough that I am ready to switch away from Ubuntu.
Maybe devuan is worth a try
(Score: 0) by Anonymous Coward on Friday January 25 2019, @09:58PM
it is