blob: 3d58f1246bdd5d109178255f5341215deb7349d2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<div class="gmail_quote">On Sat, Jul 16, 2011 at 11:37, Olivier Blin <span dir="ltr"><<a href="mailto:mageia@blino.org">mageia@blino.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Michael Scherer <<a href="mailto:misc@zarb.org">misc@zarb.org</a>> writes:<br>
<br>
> People on Fedora list were quite reluctant to changes ( to say the least<br>
> ), and I am pretty sure that someone will hit a unrelated corner case in<br>
> the last minute. Rtp was not really fond of systemd on arm and embedded<br>
> system either.<br>
<br>
</div>Do you have more details about the issues on arm/embedded?<br>
How could it be worse than forking our dozens of shell scripts?<br></blockquote><div><br>I think that it is not the case - if no specific systemd .service files are there, systemd will gladly execute initscripts init scripts.<br>
<br>Of course, there are always ordering issues, unexpected systemd-specific behavior (like accessing /dev/ being treated as service activation or such), but nothing unfixable as far as I know.<br></div></div><br>-- <br>
Eugeni Dodonov<br>
<a href="http://eugeni.dodonov.net/" target="_blank">http://eugeni.dodonov.net/</a><br>
|