Hi,<br><br> so, since I'm also migrating my system from OpenRC to systemd - pure systemd, no OpenRC compatibility, would it be any help to set the condition that ovirt-node requires systemd? I mean, the question here is ( and I think it is worth asking it ) is it worth the time and effort to keep parallel scripts and stuff? <br>
If using systemd means that, for now, init standards are no longer an issue, maybe that should be the way to go? Setup ovirt-node under systemd for now and solve init scripts problems later? Is systemd mature enough to inherit SysV or OpenRC completly? Or am I somehow wrong?<br>
My system is working with systemd quite nice, no obvious problems so far... <br><br>PS. Maybe someone could point out what is the minimal set of services needed to run on ovirt-node system/computer? So just to check if systemd has needed scripts already...<br>
<br><div class="gmail_quote">On Mon, Nov 21, 2011 at 11:58 AM, Doron Fediuck <span dir="ltr"><<a href="mailto:dfediuck@redhat.com">dfediuck@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Taking Dimitrije's issue as an example, we hit the first<br>
conflict; Gentoo is using OpenRC by default (and has some BSD-style<br>
leftovers), while RedHat and Fedora are using their SysV-style<br>
implementation, which confirms to LSB. Also, some Fedora services<br>
are moving to systemd implementation. Obviously these implementations<br>
are not trivial to bridge. So where Fedora's script will have "Required-Start:"<br>
Gentoo will use a depend() function (see vixie-cron as a sample).<br>
So unless we find a magical bridge for init standards, we'll have<br>
to have several init scripts, and each distro will use it's own<br>
script. We can try and generalize it, to make sure distor's<br>
with similar implementations use the same script.<br></blockquote></div><br>