this post was submitted on 14 Jun 2025
643 points (96.8% liked)

linuxmemes

25668 readers
953 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 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 figuresWe 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
     

    systemd cat and GNU cat hugging a Linux cat.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] ParadeDuGrotesque@lemmy.sdf.org 3 points 3 days ago (2 children)

    It's either Slackware (Linux, no systemd), OpenBSD or NetBSD.

    True story: I install a Red Hat server with a disk shelf with about 12 SAS disk in it. Red Hat has systemd. Everything works fine for a month.

    One (1) disk out of the 12 fails. No biggie. Shutdown the server cleanly. Replace disk. Flip power back on. Rebuild disk config. Simple, right?

    Wrong. You see, systemd is unhappy. It detects a new disk. It has lost a previous disk. And so, it refuses to boot. Period.

    Yes, there are ways out of this. But that was the day I decided systemd was the down of the devil.

    I once hit my head on a metal pipe

    From then forward I stopped using indoor plumbing

    [–] 4am@lemm.ee 11 points 2 days ago (1 children)

    This has never happened to me on a systemd server before. Methinks you left out some details

    [–] dukatos@lemmy.zip 2 points 2 days ago (1 children)

    Probably systemd panicked because disk id has changed. Not a reason to stop booting but that is why people hate it. Tries to handle everything, badly.

    [–] The_Decryptor@aussie.zone 3 points 2 days ago

    I mean, the point of the init process is to bring up the filesystem and disks, if the configuration is wrong that'll be the process to complain about it.