SystemD is blamed for long boot times and being heavy and bloated on resources. I tried OpenRC and Runit on real hardware (Ryzen 5000-series laptop) for week each and saw only 1 second faster boot time.

I’m old enough to remember plymouth.service (graphical image) being the most slowest service on boot in Ubuntu 16.04 and 18.04. But I don’t see that as an issue anymore. I don’t have a graphical systemD boot on my Arch but I installed Fedora Sericea and it actually boots faster than my Arch despite the plymouth (or whatever they call it nowadays).

My 2 questions:

  1. Is the current SystemD rant derived from years ago (while they’ve improved a lot)?
  2. Should Linux community rant about bigger problems such as Wayland related things not ready for current needs of normies?
  • fruitywelsh
    5·
    1 year ago

    I’m honestly a big fan. Systemd-init has tons of options like run targets, sandbox options, users you want things to run as, etc. System-oomd has tons of qol stuff for desktop users to help with stutter and responsiveness. I am also kind of excited for UKI that systemd-boot is set to support.

      • taladar@sh.itjust.works
        2·
        1 year ago

        Unified kernel image, basically a kernel and an initrd in one file that can be directly booted from UEFI. It is a bit more complicated than that but that should get you started searching for it if you want to learn more.