this post was submitted on 27 Apr 2024
-122 points (20.1% liked)
linuxmemes
21465 readers
1228 users here now
Hint: :q!
Sister communities:
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
sudoin 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!
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 fork-bomb your computer.
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
What the fuck do you do to have this happen?
Run
pacman -Syu, reboot, and it fails to boot. Had it happen many times with arch and derivatives on multiple devices. It's far more likely to happen if you don't update for like a month.Not updating in a month?! What kind of arch user is that?
A dumb one using Arch on a backup media device. At least that one dodged the bad grub release.
I've had it also happen on the main device that was updated multiple times a week.
First off, run
Syyu, the old arch gods demand itAlso have a copy of pacman-static somewhere so that you can fix your shit in case of a partial upgrade (and trust me, it can go horribly wrong)
And thirdly, Arch is meant as a power user distro -- despite this abhorrent popularity it has gained, the fact of the matter remains that you need to know the system inside and out, if you make your arch system unable to boot..... Don't use arch
This is not my attempt at elitism. Arch was never meant to be a hassle free distro and it sure as shit is not one.
There are many maintenance-free distros you can use instead. Can I offer you a Debian in these trying times?
Oh I know, I quickly learned to never update it without having live media nearby to arch-chroot with.
The only thing I did to make it unbootable is to update it. Going by that logic nobody should use it.
I definitely agree, that's why I'm commenting against dumbasses suggesting it to beginners. Especially when they glorify AUR.
No need, I already landed on MX + nix after 2+ years of arch. Nix unstable gives me all of the benefits of arch (except for the DE) and then plenty more on top. Different downsides, but far less stressful. I'm
You need to keep the update log and go through the whole thing and see if something needs reconfiguring. Sounds shitty? Yeah, that's why I stopped using Arch and Gentoo despite being a veteran
Nowadays I just install Debian or some derivative and call it a damn day. Unless you need some exotic setup (and those are more suited to Gentoo or Slackware anyway)
Oh I had a far simpler method: update and it fails to boot? Rollback and try updating again in a week. It usually works then, but I had to wait a bit more a couple of times.
The only exception was that bad GRUB release. I think that's the only update fail that absolutely required arch-chroot.
Also don't use nvidia hardware