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?
  • meteokr@community.adiquaints.moe
    link
    fedilink
    arrow-up
    3
    ·
    2 years ago

    AFAIK, nspawn is mostly a debugging tool for working with the init system without having to actually boot a live system/VM. At least that’s all I’ve ever used it for.

    • nitrolife@rekabu.ru
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      2 years ago

      It also a use case. =)

      The documentation for systemd-nspawn itself says:

      systemd-nspawn — Spawn a command or OS in a light-weight container

      The developers themselves position the daemon as a simple alternative to LXD containers.