All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: mznyfn@0pointer.de
Cc: tiwai@suse.de,
	ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	Kay Sievers <kay.sievers@vrfy.org>,
	jkysela@redhat.com
Subject: Re: [PATCHES] Integrate minimal systemd support in	alsa-utils
Date: Tue, 23 Nov 2010 08:08:12 +0100	[thread overview]
Message-ID: <4CEB685C.1030501@canonical.com> (raw)
In-Reply-To: <20101123021657.GA17275@tango.0pointer.de>

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

  parent reply	other threads:[~2010-11-23  7:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23  2:16 [PATCHES] Integrate minimal systemd support in alsa-utils Lennart Poettering
2010-11-23  6:07 ` Takashi Iwai
2010-11-23  6:16 ` Takashi Iwai
2010-11-23 17:05   ` Kay Sievers
2010-11-24  5:40     ` Takashi Iwai
2010-11-24 10:50       ` Kay Sievers
2010-11-24 11:08         ` Takashi Iwai
2010-11-24 11:04       ` Kay Sievers
2010-11-26  8:36     ` Takashi Iwai
2010-11-26 11:50       ` Kay Sievers
2010-11-26 11:57         ` Takashi Iwai
2010-11-30  6:12           ` Kay Sievers
2010-11-30  7:06             ` Takashi Iwai
2010-11-30  9:35               ` Kay Sievers
2010-11-23  7:08 ` David Henningsson [this message]
2010-11-23 11:42   ` Lennart Poettering
2010-11-23 13:55     ` David Henningsson
2010-11-23 14:58       ` Daniel Chen
2010-11-23  9:44 ` Jaroslav Kysela
2010-11-23 14:43   ` Lennart Poettering
2010-11-23 14:53     ` Jaroslav Kysela
2010-11-24 17:55 ` Colin Guthrie
2010-11-24 19:47   ` Lennart Poettering
2010-11-25 21:45     ` Colin Guthrie

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=4CEB685C.1030501@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jkysela@redhat.com \
    --cc=kay.sievers@vrfy.org \
    --cc=mznyfn@0pointer.de \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.