XPost: alt.os.linux.mint, alt.os.linux   
   From: dwhodgins@nomail.afraid.org   
      
   On Fri, 08 Sep 2023 08:18:49 -0400, Henry Crun  wrote:   
   > I am gradually moving laptop...netbook...eventully desktop from Ub. to MX.   
   > Very smooth learning curve, some advantages, some disadvantages.   
   > On Ubuntu I have been running for about  year with no snap or flatpak. If   
   only I could avoid the horror that is systemd.   
   > We are supposed to have choice, but to choose 'no systemd' immediately   
   implies 'not Ubuntu'   
   > Pity 'bout that.   
      
   When Mageia first implemented systemd, I was not in favour of it at first, but   
   decided to give it a fair chance and dig into it. After skimming through a lot   
   of documentation and experimenting with it, I changed my mind.   
      
   As leader of the qa team for Mageia linux, I had a lot more exposure than most   
   people to the problems with initd, where a change in one package would stop   
   other packages from starting and in many cases stop the system from getting   
   to a state where anyone could log in, except in run level 1. Most of those   
   mistakes were never seen by anyone other then the members of the qa team   
   and the packagers fixing the problems.   
      
   Similar mistakes in a package running under systemd are much less likely to   
   stop the system getting to a point where login is possible, and even in those   
   cases, they are much easier to fix.   
      
   There are things I don't like about systemd, such as the defaults for the max   
   size of the journal, but they are minor things that are easy to fix once you   
   understand how things work.   
      
   It's much more consistent in how things work. Instead of every package having   
   it's own custom start up script that can do things in a wide variety of ways,   
   each package has rules that systemd uses in a consistent way.   
      
   Like any init system, it has a learning curve in order to set things up   
   properly   
   both for the packagers, and for the admin of the systems using it. It does much   
   more than just replace initd, and does so in consistent logical ways.   
      
   The learning curve in order to set things up properly both for the packagers,   
   and   
   for the admin of the systems using it is steep, but so was the learning curve   
   for   
   initd when I first started using it and debugging packages that use it.   
      
   Regards, Dave Hodgins   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)