Linux

48376 readers

1748 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

132

Is Systemd that bad afterall? (sopuli.xyz)

submitted 1 year ago* (last edited 1 year ago) by Nuuskis@sopuli.xyz to c/linux@lemmy.ml

185 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] 0x0@programming.dev 0 points 1 year ago

The traditional init systems suited me just fine, i saw no need to change them. If they were so bad, then they could've been fixed or replaced.

The migration to systemd felt forced. Debian surprised everyone with the change. Also systemd's development is/was backed by corporate Red Hat, their lead developer wasn't exactly loved either and is now working for Microsoft. Of course Canonical's Ubuntu adopted it as well. Overall feels like Windows' svchost.exe, hence people accusing it of vendor lock-in.

It's not just an init system, it's way waaay more. It's supposed to be modular, but good luck keeping only its PID1 in a distro that supports systemd. It breaks the "do one thing right" approach and, in practice, does take away choice which pisses me off.

I had been using Debian since Woody, but that make me change to Gentoo on my desktop which, to me, took the best path: they default to OpenRC but you're free to use systemd if you want to. That's choice. For servers i now prefer Slackware and the laptop runs Devuan whenever i boot it up.

To be fair systemd hasn't shown its ugly face in the Ubuntu VMs i'm forced to use at work.

YMMV. If you're happy with it, fine. This, of course, is only my opinion.