this post was submitted on 29 Jun 2023

150 points (95.7% liked)

Linux

56044 readers

320 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 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

150

Is Systemd that bad afterall? (sopuli.xyz)

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

188 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?

(page 2) 50 comments

sorted by: hot top controversial new old

[–] lloram239@feddit.de 3 points 2 years ago

I am for most part quite happy with it. For all the complexity it brings, it also allows you to do a lot of stuff easily and reliable that would have been a nightmare with previous systems.

My biggest nitpick is that some commands are needlessly obtuse, e.g. trying to find an error message in journalctl is a mess when you aren't already deeply familiar with the tool. It will show you messages that are months old by default, will give exactly the same output for typos in the unit name as it will for no error messages and other little things like that.

[–] fruitywelsh@lemmy.ml 3 points 2 years ago (2 children)

I'm honestly a big fan. Systemd-init has tons of options like run targets, sandbox options, users you want things to run as, etc. System-oomd has tons of qol stuff for desktop users to help with stutter and responsiveness. I am also kind of excited for UKI that systemd-boot is set to support.

load more comments (2 replies)

[–] Vilian@lemmy.ca 3 points 2 years ago

[–] ikidd@lemmy.world 3 points 2 years ago

As a guy that's been installing Linux since you had to compile network drivers and adjust the init scripts to use them; SystemD rocks.

[–] jerrimu@lemmy.world 3 points 2 years ago (1 children)

I go crazy over boot times, systems is faster on every machine I’ve tried it on. The biggest difference I’ve seen is replacing grub, both systems-boot and car-boot seem to shave off a decent amount.

[–] Atemu@lemmy.ml 4 points 2 years ago

systemd-boot vs. GRUB should make no appreciable difference other than default timeouts and those are configurable.

[–] daemonspudguy@lemmy.fmhy.ml 3 points 2 years ago* (last edited 2 years ago)

Yes. Yes it is. systemd isn't bad for boot times, but more for tying so many goddamn things to init, PID1, creating just about the best attack point one could ever ask for. Wayland not being ready can be solved by not using it for the time being. Just use X. Also, it's still called plymouth.

[–] igorlogius@lemmy.world 2 points 2 years ago

when one just needs/wants an init system openrc is an option ... if i remember correctly systemd includes ntp, dns-resolver, ... and other stuff ... just an observation

[–] lightrush@lemmy.ca 2 points 2 years ago

Is the current SystemD rant derived from years ago (while they’ve improved a lot)?

No it's almost always been derived from people's behinds.

Should Linux community rant about bigger problems such as Wayland related things not ready for current needs of normies?

Yes.

Systemd is spectacular in many ways. Every modern OS has a process management system that can handle dependencies, schedule, manage restarts via policy and a lot more. Systemd is pretty sophisticated on that front. I've been able to get it to manage countless services in many environments with great success and few lines of code.

load more comments