this post was submitted on 29 Aug 2024
654 points (98.1% liked)
linuxmemes
21260 readers
2060 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
As a former arch linux guy, the solution to this is to be prepared by having a separate partition for home, and a bash script to reinstall f---ing everything again with a single command.
Why would you ever want to do that?
First of all, almost any Arch update induced problem can be solved by downgrading the offending package to the previous version, which handily is available in
/var/cache/pacman/pkg/
. This is an essential Arch troubleshooting skill.Even an unbootable system (which has only happened once in my 10 years of using Arch because I didn't read important news) can be fixed this way, because you can always boot from the installation usb stick and then use
arch-chroot
to access your installation and fix problems.Secondly, if the problem was indeed caused by an Arch update, you will just reinstall the problem if you run a reinstall script.
Honestly I only ever learnt Linux admin by troubleshooting my borked Arch updates, necessity being the mother of invention and all.
Ah my last reinstall was because of important news I didn't read.
Well you see, I didn't know that haha, I know there are better ways to deal with a "defective" arch update but to me, that was the easiest, laziest way to do it and it worked most of the time. I have to admit this was a "me" problem I'm not blaming arch it's just that I grew tired of things breaking because I didn't read the news before doing pacman -Syu.
You reinvented NixOS
I want to install NixOS on a laptop that I have lying around BTW.