From: David Henningsson <david.henningsson@canonical.com>
To: Lennart Poettering <mznyfn@0pointer.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [PATCHES] Integrate minimal systemd support in alsa-utils
Date: Tue, 23 Nov 2010 14:55:06 +0100 [thread overview]
Message-ID: <4CEBC7BA.4020307@canonical.com> (raw)
In-Reply-To: <20101123114222.GA24729@tango.0pointer.de>
On 2010-11-23 12:42, Lennart Poettering wrote:
> On Tue, 23.11.10 08:08, David Henningsson (david.henningsson@canonical.com) wrote:
>
>>> 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?
>
> As I wrote above it won't even be installed if systemd is not around.
Ok.
>> 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.
>
> Then disable it. And since you don't run systemd you won't even have to
> do that explicitly.
Ok; so the question is whether we should even have such a rule, and if
so, should it be enabled by default? Do other people than you and me
have an opinion here?
>>> 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.
>
> Well, this thing is far less "bloaty"
It is not bloating at all (at least not by my standard) if it's not even
installed, don't worry.
> then what Ubuntu is currently
> doing. i.e. Ubuntu duplicates the mixer init database in an init script
> /sbin/alsa-utils which is moved there for weird reasons. I can only
> encourage you to drop that "bloat" and rely on the mixer init database
> that comes with alsa, like everybody else.
>
> (Sorry, the word "bloat" just sets me off)
>
> But anyway, if you don't have systemd, you won't even see these
> files. Nothing changes for you.
>
> (Also note that Ubuntu is currently asynchronously executing said init
> script from an udev rule. That means that by the time a device added
> event reaches PA the mixer has not been configured properly yet, which
> can confused PA quite a bit. Hence please make sure to drop the
> execution of said init script from the udev rule, either by simply
> adopting the code this patch includes, or by making your current rule
> synchronous. Thanks.)
Thanks for the tip, reducing upstream delta is always a good thing. IIRC
some of it is inherited from Debian, so it wouldn't hurt for me to find
out a little more about this at that level.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2010-11-23 13:55 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
2010-11-23 11:42 ` Lennart Poettering
2010-11-23 13:55 ` David Henningsson [this message]
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=4CEBC7BA.4020307@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=mznyfn@0pointer.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.