4 May
2017
4 May
'17
6:39 p.m.
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. It has
good and bad sides, but IMO to the user it is transparent and no one should
care. And we should have some trust in the debian team and respect their
decisions.
TDE works just great with systemd, the same as without systemd ... so why
the discussion?
Back to the original topic. I installed some time ago Stretch and TDE on top
of it - just to see if all works. It works great! No issues! I must admit I
installed TDE 14.1 (devel), but I think it is not that relevant.
[tdebuildsycoca] Reusing existing tdesycoca.
tdebuildsycoca: ERROR: tde-applications.menu not found in
(/tmp/0246141687/.config/menus/,/etc/xdg/menus/)
[dcopserver] DCOP Cleaning up dead connections.
It looks like there was some problem from before ... no idea what you did.
/opt/trinity/etc/xdg/menus/tde-applications.menu
is the file in place - did you install/update/remove something
regards