SoylentNews

One of Debian's Developers Takes Vacation from Packaging systemd

posted by martyb on Monday January 21 2019, @07:14AM   
from the their-way-or-the-highway dept.

An Anonymous Coward writes:

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.]

---

Original Submission

• If scripts need improvements, update them If scripts need improvements, update them (Score: 0) by Anonymous Coward on Monday January 21 2019, @09:43PM (1 child)

  by Anonymous Coward on Monday January 21 2019, @09:43PM (#789796)

  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.

  *SPOILER* (click to show) *SPOILER* (click to hide)

  
  It's what SysV can use now, copied from /etc/init.d/lvm2-lvmpolld from a Debian (minus the header, which is a bit messy to support kFreeBSD).
  
  #! /bin/sh
  # kFreeBSD do not accept scripts as interpreters, using #!/bin/sh and sourcing.
  if [ true != "$INIT_D_SCRIPT_SOURCED" ] ; then
          set "$0" "$@"; INIT_D_SCRIPT_SOURCED=true . /lib/init/init-d-script
  fi
  

  Parent

• Re:If scripts need improvements, update them (Score: 2) by ilsa on Wednesday January 23 2019, @08:35PM

  by ilsa (6082) on Wednesday January 23 2019, @08:35PM (#790794)

  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.

  Parent