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?
  • argv_minus_one@beehaw.org
    2·
    1 year ago

    systemd is modular, but even so does break one of the core linux tenets - “do one thing well”.

    Linux itself (i.e. the kernel) breaks the hell out of that so-called core tenet. Have you looked at make menuconfig at any point? There’s everything but the kitchen sink in there.

    • digdilem
      1·
      1 year ago

      There’s been a lot of work over the years to make the kernel far more modular than it used to be and that’s why linux an run on extremely small resource footprints; because you can leave out the bits you don’t want.

    • 0x0@programming.devEnglish
      11·
      1 year ago

      Apples to oranges, and you can have a minimal kernel tailored to your needs.