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:
- Is the current SystemD rant derived from years ago (while they’ve improved a lot)?
- Should Linux community rant about bigger problems such as Wayland related things not ready for current needs of normies?
@MaxHardwood cool. Thanks. 🙂
I just noticed that it won’t work if you have a dot ‘.’ in there, e.g. ‘rsyslog.service’. It will then switch rsyslog and service around. Sadly Bash always wants to autocomplete including the *.service part. 😩
But I’m sure I’ll find other applications for this.