Description of problem:
Because of Bug 236285, we need to move ALSA volume settins from /etc to
/etc/alsa/. There's updated salsa utlity which can handle it, so we don't have
to care about alsactl any more. Proposed patch is attached.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 152898 [details]
This makes the call from something generic supported by upstream ALSA to
something RH specific. Why not just configure alsactl with a different default?
I don't think so. Upstream doesn't care about our distro specific issues, like
how we handle the module loading, where we save the configuration and so on.
But you're right. We can use "alsactl -f /etc/alsa/asound.state store". But I
prefer to have one, unified and simple command for loading/storing the volume
settings. And "salsa -l" is only a wrapper and it calls "alsactl -f
/etc/alsa/asound.state store" anyway.
There're two more benefits - if we decide to change the default we will change
only one small utility (instead of new kudzu/initscripts/udev rules changes).
And if there isn't any stored configuration (/etc/alsa/asound.state) we can
andjust the mixer with the default values (via. alsaunmute).
What version of alsa-utils does initscripts need to require/conflict with?
The updated salsa is in alsa-utils-1.0.14-0.5.rc2.fc7 so the new initscripts should:
require >= alsa-utils-1.0.14-0.5.rc2.fc7
conflict with < alsa-utils-1.0.14-0.5.rc2.fc7
Added in CVS, will be in 8.53-1.
Nope, don't add any require to alsa-utils. Initscripts does NOT depend on alsa-
utils, it only has problems with older versions, so ONLY add conflict!
alsa-utils doesn't have any requires/conflicts for initscripts because it works
fine with all versions of them.