23
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Jul 2025
23 points (89.7% liked)
Linux
12289 readers
83 users here now
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
founded 2 years ago
MODERATORS
always read the news before updates. There was one that said manual intervention was needed, and gave you the exact command you needed to run
I only read it when I get error like this to know what I shouldn't do. Is that acceptable? Always checking the news seems superfluous because most times it goes smoothly, and packman will fail and let you know if it can't do something.
I use this approach and there's never been an unrecoverable situation over the decade plus I've used Arch Linux.
to be fair this didn't break thne system either. It refused to update until you followed all 1 instructions
I've learnt to check the endeavouros forum before a kernel update (normal updates are fine), it can save you from having to chroot and tweak stuff... It takes 5 minutes to check against 2 hours to fix