Le Wed, 8 Dec 2010 00:21:08 +0000, bouleetbil (gaetan) <[email protected]> a écrit :
> Le Mon, 6 Dec 2010 01:16:44 +0100, > Miklos Vajna <[email protected]> a écrit : > > > On Sun, Dec 05, 2010 at 12:27:22PM +0100, Miklos Vajna > > <[email protected]> wrote: > > > Old action: we removed rc.modules. > > > > > > New action: ln -s systemd-modules-load.service > > > /lib/systemd/system/rc.modules.service > > > > Just a heads-up: I fixed systemd to detect rc.xxx as xxx.service > > (instead of rc.xxx.service), so that stuff that depends on > > syslog.service is started up properly (previously rc.syslog provided > > rc.syslog.service and we got broken dependencies). > > > > Also, as an example, I picked the unit file patch for alsa-utils: > > - pushed it to current _without_ removing the sysvinit script > > - reverted the alsa-utils changes in the systemd repo > > - removed the fpms from the systemd repo + used 'updatesync del > > systemd.fdb alsa-utils' to remove it from the fdb as well > > > > Bouleetbil - I hope that's OK for you. That way we can add systemd > > support in current without breaking existing users, and without having > > conflicts. :) > > Hi, > For me it's fine. We can begin to works with it and if user would use > sysvinit or systemd he can. > We should test a lot before drop sysvinit for systemd. And with this solution > we can add units step by step. > Just perhaps add 2 entries into grub : One for sysvinit (by default) and one for systemd bye -- #--------------------------------------------------------------------------- # Bouleetbil # #--------------------------------------------------------------------------- # _ _ # (o)--(o) # /.______.\ # \________/ # ./ \. # ( . , ) # \ \_\\//_/ / # ~~ ~~ ~~ #--------------------------------------------------------------------------- _______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
