this post was submitted on 07 Mar 2024
385 points (95.7% liked)

linuxmemes

21180 readers
1299 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
    385
    I know that it's rolling release, but 4 times this year seems a bit much (lemmy.world)
    submitted 8 months ago by bali10050@lemmy.world to c/linuxmemes@lemmy.world
    105 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] AeonFelis@lemmy.world 8 points 8 months ago (2 children)

    As long as I can get into the terminal I can fix the GUI. What really sucks is when it something that runs in the DM init sequence was using Python but a Python upgrade changed the import path and no it keeps restarting and I need to boot from a USB to disable that service so I can log into something and properly fix it.

    [–] adavis@lemmy.world 5 points 8 months ago (1 children)

    Pass something stupid via your bootloader so it aborts boot and dumps you in an initrd busybox shell. No usb required.

    This was my poor man's boot environments when I was using zfs on root. I had a pacman hook to snapshot before package transactions, then if it became unbootable I'd interrupt the following boot attempt, edit my grub command line with something wrong so I'd get dumped in the busybox shell, import my zfs pool and roll back before finally rebooting again.

    [–] AeonFelis@lemmy.world 1 points 8 months ago (1 children)

    That's nice. I've later googled it and found out that I could have added 3 to the end of the grub command to make it boot in runlevel 3 which does not trigger the GUI, but I guess your way could also bypass boot issues that prevent even non-gui boot.

    I also see that there is runlevel 1, which is kind of an emergency mode, so maybe that would be the best thing to use?

    [–] adavis@lemmy.world 1 points 8 months ago

    Yeah for my case it was easier in the initrd otherwise I'd be trying to roll back the active / partition.

    Re run levels, they were a sysvinit thing so I wasn't sure sure about systemd, this suggests that would work though https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet

    And if you have to bail out even earlier, run level 1 will give you the rescue.target

    [–] 4RCH_U53R@lemmy.world 1 points 8 months ago

    damn thats oddly specific XD