this post was submitted on 11 Mar 2024
341 points (97.5% liked)

linuxmemes

21226 readers
73 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!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    341
    When I try to debug an issue on the OS side after a kernel update but it's fixed by unplugging the power cable for a few minutes. (infosec.pub)
    submitted 8 months ago by prof@infosec.pub to c/linuxmemes@lemmy.world
    20 comments fedilink hide all child comments
     

    Totally not based on a true story.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] DumbAceDragon@sh.itjust.works 9 points 8 months ago* (last edited 8 months ago)

    This actually happened to me not too long ago. Things would randomly just crash. Turns out it was because my RAM had bad sectors in it.

    On linux I'd just restart whatever crashed and it usually went along fine for another 30 minutes. Worst that happened was btrfs would make my drive readonly until a reboot because it knew some shit was up.

    On windows it bluescreened several times before corrupting the hard drive (was thankfully able to recover it lol)