linuxmemes

24236 readers

1835 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

Instance-wide TOS: https://legal.lemmy.world/tos/
Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html

2. Be civil

Understand the difference between a joke and an insult.

Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".

Don't get baited into back-and-forth insults. We are not animals.

Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.

Bigotry will not be tolerated.

3. Post Linux-related content

Including Unix and BSD.

Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.

No porn, no politics, no trolling or ragebaiting.

4. No recent reposts

Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.

5. 🇬🇧 Language/язык/Sprache

This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸

Comments written in other languages are allowed.

The substance of a post should be comprehensible for people who only speak English.

Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.

6. (NEW!) Regarding public figures

We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.

Keep discussions polite and free of disparagement.

We are never in possession of all of the facts. Defamatory comments will not be tolerated.

Discussions that get too heated will be locked and offending comments removed.

Please report posts and comments that break these rules!

Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

founded 2 years ago

MODERATORS

poopsmith@lemmy.world

zephyr@lemmy.world

rtxn@lemmy.world

696

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

submitted 2 years ago by MashedTech@lemmy.world to c/linuxmemes@lemmy.world

144 comments fedilink hide all child comments

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

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

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

[+] histy@lemmy.world 29 points 2 years ago* (last edited 1 year ago) (2 children)

[deleted]

[–] Rodeo@lemmy.ca 8 points 2 years 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.

[–] namingthingsiseasy@programming.dev 8 points 2 years 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.