Linux

1257 readers

75 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

145

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

238 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

[–] eleitl@lemmy.ml 2 points 1 year ago (2 children)

The problem of systemd is that it hasn't been just a replacement of init as they initially claimed, and now deny they ever did. Things like Mono, Gnome and systemd are bad for the ecosystem long term.

An init done by constructive people wouldn't be a problem at all.

[–] Fryboyter@discuss.tchncs.de 6 points 1 year ago (1 children)

The problem of systemd is that it hasn’t been just a replacement of init as they initially claimed

Apart from the PID 1 part of systemd, almost all tools are optional.

Although I have a positive opinion about the systemd project, I used netctl instead of systemd-networkd for a long time without any problems. And even today I don't use systemd-resolved because I use a combination of unbound and Pi-Hole in my private LAN. And so on.

So you can't say that the systemd project has replaced various solutions in such a way that you don't have a choice anymore.

[–] eleitl@lemmy.ml 1 points 1 year ago

I was more referring to things like e.g. https://wiki.gentoo.org/wiki/Hard_dependencies_on_systemd

Notice that it's from 2021 and just for Gentoo. This is what people politely describe as invasive.

[–] monkeysuncle 1 points 1 year ago

How is Gnome bad for the ecosystem long term? I get that there are things that the Gnome devs do which are controversial, and they have no problem removing options from their own projects, but they have also created a fairly cohesive user experience. I'm currently running KDE, and there is a lot I don't like about some of Gnome's choices, but I don't think they are bad for the ecosystem.