On Fri, Nov 26, 2010 at 09:36, Takashi Iwai <tiwai@xxxxxxx> wrote: > At Tue, 23 Nov 2010 18:05:00 +0100, > Kay Sievers wrote: >> >> On Tue, Nov 23, 2010 at 07:16, Takashi Iwai <tiwai@xxxxxxx> 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 > Yes, so: systemctl start alsasound.service works, and the old init script is not started anymore by the SVSV compat code. > corresponding to /etc/init.d/alsasound, while keeping > /etc/init.d/alsasound as is? Yes, for non-systemd boots. > If so, this will also belong to alsa-utils.rpm, I suppose. ÂOtherwise > we'll get a circular dependency. Sure, it does not matter as long as the link is there. :) Thanks a lot, Kay _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
