this post was submitted on 16 Jul 2023
426 points (100.0% liked)

linuxmemes

21263 readers
485 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
    426
    Btw (i.imgur.com)
    submitted 1 year ago by muhyb@programming.dev to c/linuxmemes@lemmy.world
    36 comments fedilink hide all child comments
     

    I’m moving my posts from Reddit to Lemmy before delete them.

    This post is from 2020-08-12.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] MentalEdge@sopuli.xyz 4 points 1 year ago (1 children)

    When you install or update something that breaks something, like has happened to me many times, to the point that the system cannot boot, you can pick a snapshot from the grub menu from before those changes occurred, allowing you to recover your system to a working state without the use of a live boot usb.

    It's also been useful when some program or other stops working due to some change in a dependency somewhere, like OBS sometimes does. Then you can just hop backwards in time to a point where it works and get to actually using your system, instead of spending hours tracking down exactly where an error is occurring right then and there. "fixing it later" becomes a valid way of dealing with problems with your system, when just pressing a button lets you make it temporarily go away.