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?
  • nyan@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    In all fairness, a lot of it is sort of optional if you’re compiling your own copy from source . . . which no one outside of Gentoo (/Funtoo/Pentoo/Sourcemage/LFS) ever does. I just had a look at the ebuild for systemd 253.5, and there are 37 USE flags, most of which translate directly to build options. Just figuring out which bits you want could take hours.

    • Alex
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Sourcemage, now there’s a distro I haven’t heard about for a long long time.