On 2010-11-23 03:16, Lennart Poettering wrote: > Heya, > > Up to this point most distributions have been using different init > scripts/udev rules files to save/restore mixer settings at > boot/hotplug/shutdown. Please see my two attached patches for alsa-utils > which add standardized, simplified support for this. > > The first patch is stolen from Debian/Ubuntu, which moves asound.state > to /var/lib, which is a more appropriate place, since /etc might be > read-only. > > The second patch includes a minimal udev rule (executed synchronously, > enabled on all systems, regardless of systemd is used or not) and two > systemd service files (executed asynchronously at boot/shutdown, only > enabled if built with systemd support). Lennart, Could you clarify how this affects/changes behaviour for distros not running systemd? Also, I personally don't like the idea of saving the mixer state at shutdown. (Although I know Ubuntu has that as well.) Too many times I have cranked up the volume for some reason, then turned the computer off, only to find the login sound at maximum volume. > Given that most big distributions are moving to adopt systemd sooner or > later That assumption is not necessarily true at this point. AFAIK, it remains to be seen. That said, I don't mind a systemd patch into alsa-utils, as long as it doesn't break or bloat anything for non-systemd distros. -- David Henningsson, Canonical Ltd. http://launchpad.net/~diwic _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
