James Lee wrote:
>> If you are using build 115 or later, which uses OSS,
>> then you can do
>> the following:
>>
>> 1) Set the audio settings as you would like them to
>> be on reboot.
>> 2) Run
>>
>>     $ mixerctrl -s (filename)
>> Then make sure that your system runs the following
>> command when it
>>     boots up, or when your user session starts up:
>>  $ mixerctrl -r (filename)
>> For example, you could put this command in your
>>  user's $HOME/.profile
>> if you want it to reload the settings for just
>>  your user.  Or, if you
>> want it to load the settings for all users, you
>>  could put it in the
>> GDM Init or PreSession script.  Info about the GDM
>>  scripts is here:
>> http://library.gnome.org/admin/gdm/2.28/configuration.
>> html.en#scripting
>>
>> If you wanted to save the settings on each user
>> logout and reload them
>> on each user login, then I would recommend running
>> the "mixerctrl -s"
>> command in the GDM PostSession script and the
>> "mixerctrl -r" in the
>> GDM PreSession script.
>>
>> Hope this helps,
>>
>> Brian
>>     
>
> I've created an SMF service to automate saving and loading the volume on 
> shutdown and bootup which I think is more appropriate than using GDM.  See 
> http://thestaticvoid.com/post/2009/11/25/mixer-state-in-opensolaris/ if 
> you're interested.
>   

The SMF service would save and restore "master" settings, but doesn't do 
anything for individual user-preferences.

By the way, I'm planning on replacing mixerctl with an easier to use 
interface called audioctl.  Since mixerctl has only been in development 
builds so far, I figure such a change is fair game. :-)  See PSARC 
2009/626 for details.

    - Garrett

> James
>   

Reply via email to