Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paul Menzel <paulepanter@users.sourceforge.net>
Cc: alsa-devel@alsa-project.org, Jordi Mallach <jordi@debian.org>
Subject: Re: [PATCH] alsactl: Check existence of `alsactl` in udev	rule
Date: Fri, 30 Dec 2016 11:16:11 +0100	[thread overview]
Message-ID: <s5hr34pzpqs.wl-tiwai@suse.de> (raw)
In-Reply-To: <1483092294.3846.46.camel@users.sourceforge.net>

On Fri, 30 Dec 2016 11:04:54 +0100,
Paul Menzel wrote:
> 
> Am Donnerstag, den 29.12.2016, 14:28 +0100 schrieb Takashi Iwai:
> > On Wed, 28 Dec 2016 23:31:15 +0100,
> > Paul Menzel wrote:
> > > 
> > > From: Jordi Mallach <jordi@debian.org>
> > > Date: Thu, 10 Jan 2013 00:17:58 +0000
> > > 
> > > Include the line `TEST=="/usr/sbin/alsactl"` in the udev rule, to
> > > properly fix the state restoring for users with split `/usr`
> > > filesystems
> > > [1].
> > 
> > This doesn't sound like a real "fix".  It means that the whole
> > save/restore mechanism will be silently lost, right?
> 
> Well, if the binary `alsactl` is not available, it shouldn’t be run.
> 
> But you are right, it depends on the system setup, what happens.
> 
> See the description of commit de7c3eff (alsactl: systemd and udev
> hookup).
> 
> >     - At boot the asound.state file might not be readable, since it resides
> >       on a different file system. That means exclusively restoring sound card
> >       settings from udev rules will no suffice, since if the rule is
> >       executed at early boot (for example within udev settle) then the file
> >       will no be readable and cannot be restored.

Yeah, if you allow a separate /usr partition to be mounted later, all
stuff executed in udev rules should be put in either /bin or /sbin.
The same is true for /var/lib/alsa.

And yet the question is whether we should suppress the error in such a
case.  When suppressed, user might not notice what went wrong.
Meanwhile an error message is annoying if you know it.


Takashi

> 
> 
> Thanks,
> 
> Paul
> 
> 
> > > Upstream the patch from the Debian package [2].
> > > 
> > > [1] https://bugs.debian.org/670490
> > >     "Debian Bug report logs - #670490 alsa-utils: Restore sound volume
> > >      in udev"
> > > [2] https://sources.debian.net/src/alsa-utils/1.1.2-1/debian/patches/udev_test_alsactl.patch/
> > > 
> > > Signed-off-by: Paul Menzel <paulepanter@users.sourceforge.net>
> > > CC: Jordi Mallach <jordi@debian.org>
> > > ---
> > > Please apply with `git am saved-messages.mbox`.
> > > 
> > >  alsactl/90-alsa-restore.rules.in | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/alsactl/90-alsa-restore.rules.in b/alsactl/90-alsa-restore.rules.in
> > > index c0c1b23..f190b85 100644
> > > --- a/alsactl/90-alsa-restore.rules.in
> > > +++ b/alsactl/90-alsa-restore.rules.in
> > > @@ -2,7 +2,7 @@ ACTION=="add", SUBSYSTEM=="sound", KERNEL=="controlC*", KERNELS!="card*", TEST==
> > >  GOTO="alsa_restore_end"
> > >  
> > >  LABEL="alsa_restore_go"
> > > -TEST!="@daemonswitch@", RUN+="@sbindir@/alsactl restore $attr{device/number}"
> > > -TEST=="@daemonswitch@", RUN+="@sbindir@/alsactl nrestore $attr{device/number}"
> > > +TEST!="@daemonswitch@", TEST=="@sbindir@/alsactl", RUN+="@sbindir@/alsactl restore $attr{device/number}"
> > > +TEST=="@daemonswitch@", TEST=="@sbindir@/alsactl", RUN+="@sbindir@/alsactl nrestore $attr{device/number}"
> > >  
> > >  LABEL="alsa_restore_end"
> > > -- 
> > > 2.11.0
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2016-12-30 10:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-28 22:31 [PATCH] alsactl: Check existence of `alsactl` in udev rule Paul Menzel
2016-12-29 13:28 ` Takashi Iwai
2016-12-30 10:04   ` Paul Menzel
2016-12-30 10:16     ` Takashi Iwai [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hr34pzpqs.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jordi@debian.org \
    --cc=paulepanter@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox