[Pkg-alsa-devel] Re: Bug#375388: More info about alsa-utils
incorrect reportbug
Elimar Riesebieter
riesebie at lxtec.de
Fri Jun 30 06:27:17 UTC 2006
On Thu, 29 Jun 2006 the mental interface of
Dan Chen told:
> --- Elimar Riesebieter <riesebie at lxtec.de> wrote:
> > There is one thing as mentioned in a later mail as
> > well:
> >
> > How do we handle Bug#375388?
>
> I'm pretty sure that we need neither $syslog nor $remote_fs.
[...]
On Tue, 27 Jun 2006 the mental interface of
Carlos Villegas told:
> Elimar Riesebieter wrote:
> >I can not figure out a bug or something else here?
> >### BEGIN INIT INFO
> >#..
> >### END INIT INFO
> >is realy only an INFO. But I can not identify the reason for this
> >comments at the moment (:
>
[...]
> Coming back to alsa-utils case, the bug reported was related to the service
> required. According to the current information in the init script:
>
> ### BEGIN INIT INFO
> # Required-Start: $syslog $remote_fs
> # Required-Stop: $syslog $remote_fs
> # Default-Start: S
> # Default-Stop 0 6
> # Short-Description: Restore and store ALSA driver settings
> ### END INIT INFO
[...]
> >But anyway, do you have problems running sound applications using
> >alsa?
>
> no, i have no problems running it but I don't how alsa-utils works and why it
> would or wouldn't require the system log to be started ($syslog).
[...]
I managed the initscript als follows:
Index: init
===================================================================
--- init (Revision 1676)
+++ init (Arbeitskopie)
@@ -3,8 +3,7 @@
# alsa-utils initscript
#
### BEGIN INIT INFO
-# Required-Start: $syslog $remote_fs
-# Required-Stop: $syslog $remote_fs
+# Required-Start: mountall
# Default-Start: S
# Default-Stop 0 6
# Short-Description: Restore and store ALSA driver settings
Elimar
--
>what IMHO then?
IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
--posting from alex in debian-user--
More information about the Pkg-alsa-devel
mailing list