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?
[pi@raspberry]# sudo suJust saying, not everyone needs session management…
Why spawn additional process when you can get into shell directly with
sudo -s?Well, sudo itself is a purely optional component—you can run a system quite happily with just su .
What do you do with all the process you save with that trick ?
Because I already had my fingers closer to “su” than to “-s”… but more seriously, because I tend to use
sudo -E suon a remote terminal with a PS1 set to colorize the prompt based on whether I’m running root and the host if it’s remote, butsudo -E -sdoesn’t run the root’s.bashrcthat runs the updated colorization while at the same time exports too much of the user’s environment into the root shell.