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?
  • neekz0r
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    environment variables are the way to go, though. It’s how most modern software is configured in modern platforms (eg: an application in kubernetes is presented env vars sourced from a configmap).

    init scripts were flawed, but to say they are bad because their environment variables changed their behavior isn’t a good stance, imho.