Bug#375388: [Pkg-alsa-devel] Bug#375388: Incorrect boot order of alsa-utils and sysklogd

Elimar Riesebieter riesebie at lxtec.de
Sun Jun 25 19:17:21 UTC 2006

tag 375388 moreinfo

On Sun, 25 Jun 2006 the mental interface of
Carlos Villegas told:

> Package: alsa-utils
> Version: 1.0.11-4
> alsa-utils script in the initscripts requires the metapackage $syslog (i.e. 
> sysklogd or syslog scripts) to start but it is ordered to start before it. The 
> reason for this is that S50alsa-utils is placed on the /etc/rcS.d/ symbolic 
> link pool while S10sysklogd is in /etc/rc2.d/.
> $ less /etc/rcS.d/S50alsa-utils
> ....
> # Required-Start:    $syslog
> ...
> $ ls /etc/rc2.d
> ...
> S10sysklogd
> ...
> I suggest that the script's symbolic link is placed on /etc/rc2.d instead of 
> /etc/rcS.d. Any order above 10 should do. /etc/rc2.d/S15alsa-utils works for 
> me. Besides, if lintian or linda would report when dependency information is 
> missing, it would be easier to use a script adjust the order of the init 
> scripts to ensure that these are met for each system (as dependency information 
> would be available).

/etc/init.d/alsa-utils does:
Restore and store ALSA driver settings

The only assumption is, that /var must be mounted before running the
script, becaud it reads and writes /var/lib/alsa/asound.state.

Did I missunderstood something?


  Experience is something you don't get until 
  just after you need it!

More information about the Pkg-alsa-devel mailing list