On Sun, Apr 30, 2017 at 21:23 (+0200), deloptes wrote: > Keith Daniels wrote: >> My bias is anti systemd, just so you know.-- scant documentation >> and there has never been a security review of its package. > Meanwhile the situation has improved . There are many things > improved including documentation. What I can recommend is the > "systemd cheat sheet" which can be found in different flavors > around. > Just few examples. > https://wiki.debian.org/systemd/CheatSheet > https://gist.github.com/mbodo/8f87c96ce11e91f80fbf6175412a2206 > My personal experience is ... after looking into it I used systemd > free debian for some time until I was ready to move my system to > systemd. It took me few hours ... mainly fixing some custom > networking logic (scripts that would execute on certain conditions) > and migrating few scripts. > Since than I can not complain. I moved all systems from init to > systemd - no issue. > I can just conclude that the main problem is the unwillingness to > grow. I don't know whether that is merely a poorly-thought out idea or a deliberately abrasive obnoxious over-generalization. There is a lot of debate about the merits of systemd, and some people have come to the conclusion (rightly or wrongly) that they would prefer to not use it in their system. > Of course I can understand this - why fixing something again after > some 10-15y when it was working flawlessly ... Are you talking about ("somethign") SysV (or BSD) init scripts? 10-15 years? Perhaps more like 40 years. > but guys this is called evolution - for good or for bad. So if it is possibly bad, why would we want to evolve in that direction? I use Slackware, and the guy in charge has made the conscious decision to not use systemd, and it seems like he is unlikely to change that any time soon. There are currently other distros with similar strategies. Do people working on Trinity really want to alienate people who use systemd-free distros? That seems like a bad idea to me, but that is just my opinion. Jim