From: Takashi Iwai <tiwai@suse.de>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
jkysela@redhat.com, Lennart Poettering <mznyfn@0pointer.de>
Subject: Re: [PATCHES] Integrate minimal systemd support in alsa-utils
Date: Fri, 26 Nov 2010 09:36:14 +0100 [thread overview]
Message-ID: <s5hmxowqy69.wl%tiwai@suse.de> (raw)
In-Reply-To: <AANLkTikbP_yRSDWD1DL0EKza=EpRdnDHLpUMhoXVnDiE@mail.gmail.com>
At Tue, 23 Nov 2010 18:05:00 +0100,
Kay Sievers wrote:
>
> On Tue, Nov 23, 2010 at 07:16, Takashi Iwai <tiwai@suse.de> wrote:
>
> > The second patch looks good to me. It doesn't break, at least.
> > I'm going to apply it unless anyone else has specific objection.
>
> Now that both is merged, mind putting that in openSUSE Factory?
>
> We need to enable systemd services with:
> --with-systemdsystemunitdir=/lib/systemd/system
>
> list the files/dirs in:
> /lib/systemd/system/*.service
> /lib/udev/rules.d/*.rules
>
> Drop the current custom udev rule:
> /etc/udev/rules.d/40-alsa.rules
> and use only the systemd one in /lib/udev/. It should work also for
> non-systemd setups.
>
> All the naming rules for the snd/ subdir can be removed on all recent
> systems, only the GROUP="audio" is needed.
>
> No rules files should be installed in /etc, all files from packages
> belong into /lib.
Now I fixed all these on OBS multimedia:libs project.
The only question is the below one:
> The old SYSV init script:
> /etc/init.d/alsasound
> should be linked to:
> /lib/systemd/system/alsasound.service -> alsa-restore.service
> so that the init script will not be executed on systemd bootups.
Do you mean to create a symlink
/lib/systemd/system/alsasound.service -> alsa-restore.service
corresponding to /etc/init.d/alsasound, while keeping
/etc/init.d/alsasound as is?
If so, this will also belong to alsa-utils.rpm, I suppose. Otherwise
we'll get a circular dependency.
thanks,
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-11-26 8:36 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 [this message]
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
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=s5hmxowqy69.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=jkysela@redhat.com \
--cc=kay.sievers@vrfy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox