Dev1 Galaxy Forum / Missing init scripts and how to provide them

Re: Missing init scripts and how to provide them

dummy@example.com (igorzwx) — Fri, 14 Jun 2024 17:05:54 +0000

$ /etc/init.d/alsa-utils
Usage: /etc/init.d/alsa-utils {start [CARD]|stop [CARD]|restart [CARD]|reset [CARD]}

Re: Missing init scripts and how to provide them

dummy@example.com (bai4Iej2need) — Fri, 14 Jun 2024 16:46:02 +0000

Hi
I tested this script sysd2v.sh and it failed.
The start stop functions were not created.

YMMV.

Re: Missing init scripts and how to provide them

dummy@example.com (Head_on_a_Stick) — Sun, 13 Feb 2022 20:43:03 +0000

This is generated from /lib/systemd/system/alsa-restore.service in my Arch box:

#!/bin/sh
# Generated by sysd2v v0.3  --  http://www.trek.eu.org/devel/sysd2v
# 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
### BEGIN INIT INFO
# Provides:       alsa-restore
# Required-Start: $remote_fs
# Required-Stop:  $remote_fs
# Default-Start:  2 3 4 5
# Default-Stop:   0 1 6
# Description:    Save/Restore Sound Card State
### END INIT INFO
DESC="alsa-restore"
DAEMON=none
PIDFILE=none

do_start_cmd_override ()
{
  /usr/sbin/alsactl restore
  true
}

do_stop_cmd_override ()
{
  /usr/sbin/alsactl store
  true
}

do_status_override () :

^ Save that to /etc/init.d/alsa-restore and run

# update-rc.d alsa-restore defaults

Disclaimer: untested.

Re: Missing init scripts and how to provide them

dummy@example.com (MLEvD) — Sun, 13 Feb 2022 18:09:44 +0000

Is there some way to reinstate the missing alsa restore and save sound card state in devuan?

Missing init scripts and how to provide them

dummy@example.com (Head_on_a_Stick) — Sun, 06 Feb 2022 20:19:17 +0000

With the advancing encroachment of systemd across the Linux ecosystem it is now not unusual for applications to only supply systemd unit files and omit traditional init scripts. This prevents users of alternative init systems from automatically starting system daemons and other services at boot.

For the bullseye release Debian has provided a small selection of "orphaned" init scripts that can be installed in Devuan chimaera (or later) with

# apt install orphan-sysvinit-scripts

A list of the scripts and their locations can be found here:

https://packages.debian.org/bullseye/al … s/filelist

To use the scripts copy them from /usr/share/orphan-sysvinit-scripts/ to /etc/init.d/ and run this command to make them start automatically from the next boot:

# update-rc.d script defaults

To start the script immediately use

# service script start

In both cases replace script with the actual name of the file that was copied to /etc/init.d/.

For the applications not covered by the above package there is a sysv2d.sh script that can be downloaded from here by using this command:

$ wget https://git.savannah.nongnu.org/cgit/sysvinit.git/plain/contrib/sysd2v.sh

To use it make the script executable and move it to a directory in your user's PATH:

$ chmod +x sysd2v.sh
# mv sysd2v.sh /usr/local/bin/sysd2v

Once that is done the command can be used on any systemd unit files[1] like this:

$ sysv2d example.service > example
# mv example /etc/init.d/

In both commands replace example with the actual name of the unit file.

Once the script is moved to /etc/init.d/ it can be enabled with update-rc.d and started with service as outlined earlier.

(In this thread commands prefixed with $ should be run as the normal user and commands prefixed with # should be run as root; in both cases the prefix should be omitted when running the actual command.)

[1] The systemd .service unit files for installed packages can be found under /lib/systemd/system/.