this post was submitted on 06 Aug 2025
362 points (95.0% liked)

linuxmemes

26696 readers
358 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
    you are viewing a single comment's thread
    view the rest of the comments
    [–] DonutsRMeh@lemmy.world 22 points 1 week ago (2 children)

    Been using Linux as my main system for about 8 years now. I know nothing but systemd. I have never tried other init systems, so I genuinely don't know what I'm missing out on (if there is any). I don't mind systemd and I really really like services and timers. I use them all the time to automate things, but that doesn't mean I don't hate some things about systemd. One of the things that I'd love to burn to charcoal is that "a stop job for UID 1000..... 1:45 minutes", bitch? I don't have that much time on my hands, reboot right now. What are the things that other init systems have that make them better than systemd?

    [–] WhyJiffie@sh.itjust.works 10 points 6 days ago

    a stop job for UID 1000..... 1:45 minutes

    oh oh and then it changes to 3 minutes something when 1:45 passes! where was that configured mr poettering??

    [–] Statick@lemmy.world 1 points 6 days ago (2 children)

    Enable SysRq commands and ALT+SysRq(same as print screen)+B to force reboot

    [–] rtxn@lemmy.world 5 points 6 days ago

    You really shouldn't do that. SysRq reboot is like SIGKILL on steroids. If the OS hasn't flushed and closed every file handle, you can corrupt the shit out of the system. Ask me how I know.

    You can skip waiting for services to stop by pressing Ctrl+C eight times within two seconds. If you really need to reboot using SysRq, then at least do a sync (Alt+SysRq+S) before that.

    [–] DonutsRMeh@lemmy.world 1 points 6 days ago

    I just set the timeout time to 5 seconds.