On 04/05/2017 19:39, deloptes wrote:
> Mike Bird wrote:
>
>> It seems extraordinarily unlikely that Tim would make such a mistake but
>> if TDE broke sysvinit support or required systemd we would be unable to
>> continue with TDE, just as we now use Devuan instead of Debian.
> The fact is that TDE does not care much. I switched to systemd completely
> few months ago with no issues. I had only one script that would run the
> firewall when in public LAN and I was instructed to put it
> under /etc/network/if-up.d/. This worked great - about 20min of work to
> adapt the script and it was over.
> On the server I have like 10 custom scripts in init.d and all work
> independent of systemd.
> On a custom firewall (exotic hardware) I add the boot option
> init=/lib/sysvinit/init and let systemd install. Works also great!
>
> I really don't understand what is this frustration about systemd.

First and foremost, choice. With debian, you no longer have one. There 
is more too it of course, but I'm done with the flame wars, I've turned 
to devuan .....

-- 
Mike Howard