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

    Systemd (PID1) is not your boot manager, network deamon, resolver, user manager or ntp service.

    Those are entirely independent deamons that happen to be developed under the systemd project umbrella but can be exchanged for equivalent components.
    Tkey are gully optional.

    In many cases, the systemd project’s one is one of the best choices though, especially when used with other systemd-developed components.
    In some cases, there is no other viable choice because the systemd-* is just better and nobody wants to deal with something worse.