I have seen so many times that systemd is insecure, bloated, etc. So i wonder ¿does it worth to switch to another init system?

  • TCB13@lemmy.worldEnglish
    6·
    10 months ago

    That list of “features” never needed to be replaced by systemd and for the most part are provided by the other init offerings.

    This is plain wrong. Init wasn’t able to properly start things in parallel and monitor them. With systemd you can even create a visual representation graph of your boot services that you can use to identify what is taking more time and when things are happening.

    What’s wrong with ip, iproute2, iptables/nftables, ufw, firewalld, ntp, dnscrypt, privoxy, dnsmasq, openresolve, crond, sudo, mount, syslog-ng?

    What’s wrong? Too many tools, way too fragmented and poorly integrated. It is very, very easy to get into trouble if you simply setup a dual stack system with IPv6-PD with those tools. With systemd it all works of the box with simples configuration files and its way more intuitive. For eg. cron is a mess, systemd timers share the unit config format which is way better and more scalable.

    I use systemd and have disabled much of it

    So you are saying you could just have a very small footprint and have a very lightweight system that is very solid but instead of choose to go with a bunch of different tools? I’ve leveraged systemd to be able to have fully working system on devices with 256MB of RAM while still having RAM for other important applications.

    • t0m5k1@lemmy.world
      3·
      10 months ago

      Here’s a handy chart for you

      https://wiki.gentoo.org/wiki/Comparison_of_init_systems

      As you can see many have the ability to start services in parallel. Some script magic with graphviz will also do similar to analyse blame.

      What’s wrong? Too many tools, way too fragmented and poorly integrated. It is very, very easy to get into trouble if you simply setup a dual stack system with IPv6-PD with those tools. With systemd it all works of the box with simples configuration files and its way more intuitive. For eg. cron is a mess, systemd timers share the unit config format which is way better and more scalable.

      Do you honestly beloved thie mental gymnastics your getting into just to prove your point, go back to windows. Lol

      Well done on using systemd how you wish, now move on and let others use it how they wish or remove it.

      • TCB13@lemmy.world
        3·
        10 months ago

        It’s not gymnastics, it’s years and years of init bullshit and fragmentation / lack of integration related issues that were solved by systemd.