this post was submitted on 03 Oct 2023
693 points (93.6% liked)

linuxmemes

21607 readers
866 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • 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.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 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. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
    •  

    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 fork-bomb your computer.

    founded 2 years ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    693
    I'm probably going to get a lot of explanations in the comments (lemmy.world)
    submitted 1 year ago by [email protected] to c/[email protected]
    145 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 8 points 1 year 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.