linuxmemes

20731 readers

1464 users here now

I use Arch btw

Sister communities:

LemmyMemes: Memes
LemmyShitpost: Anything and everything goes.
RISA: Star Trek memes and shitposts

Community rules

Follow the site-wide rules and code of conduct
Be civil
Post Linux-related content
No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago

MODERATORS

poopsmith@lemmy.world

zephyr@lemmy.world

693

I'm probably going to get a lot of explanations in the comments (lemmy.world)

submitted 11 months ago by MashedTech@lemmy.world to c/linuxmemes@lemmy.world

145 comments fedilink hide all child comments

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

[–] TimeSquirrel@kbin.social 145 points 11 months ago* (last edited 11 months ago) (21 children)

I'm going to create a distro where EVERYTHING including your web browser is launched through systemd and it's built from nothing but snaps, just for you guys. I'll call it "Oops! All snaps."

[–] someacnt@sopuli.xyz 15 points 11 months ago (2 children)

What's with all the systemd hate? It seems to work well for me..

[+] histy@lemmy.world 29 points 11 months ago* (last edited 11 months ago) (2 children)

[deleted]

[–] namingthingsiseasy@programming.dev 8 points 11 months ago

Another problem is that there is (or was, I don’t follow these things) friction between the Kernel and systemd, as systemd developers did not respect certain development philosophies.

More information on this here:

When systemd sees "debug" as part of the kernel command-line, it will spit out so much informaiton about the system that it fails to boot... The init system just collapses the system with too much information being sent to the dmesg when seeing the debug option as part of the kernel command-line parameter. Within the systemd bug report it was suggested for systemd not to look for a simple "debug" string to go into its debug mode but perhaps something like "systemd.debug" or other namespaced alternatives. The debug kernel command-line parameter has been used by upstream Linux kernel developers for many years. However, upstream systemd developers don't agree about changing their debug code detection. Kay Sievers of Red Hat wrote, "Generic terms are generic, not the first user owns them."

tl;dr: systemd parsed kernel command line information; when "debug" was present, systemd enabled logging that was so verbose that it would cause the system to become unbootable. systemd developers were notified of the issue and started acting passive aggressive instead of fixing the issue.

Or to put it more simply: if you make changes that cause Linus Torvalds' system to stop booting properly, you're probably gonna have a bad time.

[–] Rodeo@lemmy.ca 8 points 11 months ago

Don't forget the development issues. Last I read up on this was several years ago, so things may have changed, but:

It's open source, but it's entirely controlled by a handful of people who work for RedHat, and they don't publish any of their communications about development nor any supporting material like code documentation. It's a massive complicated codebase and they've made no effort to make it accessible, nor do they allow contributions from anyone outside the RedHat team, so it remains a closed black box controlled by a private, for profit corporation.

It's open source in the worst way possible.

load more comments (18 replies)