Lol this is still me after 20 years of using linux
linuxmemes
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 users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
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 remove France.
Right? Decades of Linux use, been a Linux admin for half of it. Still reinstall when I'm not happy with the way things are going. It's just faster.
Yeah fedora screwed up TODAY so I'm just reinstalling
And running into issues encrypting my swap so wishing I had just tried to solve the problem :p
The fresh feeling of a reinstall lasts for about a week.
Then there's the cloud: "Oh, crap. I have a typo in a config file. I guess I'll destroy the machine and set up a whole new one!"
I did this without having my distro broken. It was like "oh shiny, let me try this distro"
Honesty just make /home a different partition.
Has saved me so much trouble in changing distros on my laptop.
Iβve settled pretty well on Fedora at this point but thatβll probably change at some point (mostly because I donβt like Ubuntu much and I work in a mostly RHEL shop)
Being able to easily and freely upgrade, experiment, and reinstall is one of the big perks of Linux. Carry on.
I reinstalled Linux when it crashes, or used Timeshift for years, but at this time I learned totally nothing.
Then I tried Arch manual installation, and it changes my mind.
Reminds me, that I want to "fix" my install.
Ah, the Windows approach. The few times I worked with PC Repair shops, backing up everything and reinstalling the OS was the go to for most "repairs". Especially since it was faster and cheaper than just researching all the issues and repairing them the "right" way. Although to be fair, if the OS is borked enough, backup + reinstall IS the right way.
Broke my ZorinOS install by trying to upgrade parts of the OS by myself so I could run newer software and lived like that for months until I gave up and switched to Fedora
Iβm on Unraid now and have most of my services migrated to docker containers but on my previous build, I was just running Ubuntu Server a majority of the time.
I got a little scared thinking about all of the manual configuration Iβve done over time to this build and knew that if I needed to reinstall Iβd essentially be fucked.
Like what tf is a fstab again?
So I took a few hours to learn Ansible and wrote a playbook that could configure my build nearly 100% in just one click. Changed the game.
If anyone knows of something similar with Unraid configs let me know bc I really did enjoy the ansible process
Literally this morning I started getting boot errors. It is telling me WBM can't find the boot file. But I should be booting into grub, so idk what to do. My boot order is Ubuntu, then USB. And that's it. And now I'm out of the house all day and can't do anything but sweat about it.
have / on one partition and /home on another, when reinstalling, reformat or reuse / and set the other as /home again. Worked very well when I switched from Ubuntu to Manjaro last week when Ubuntu refused to boot up for me for no obvious reason.
Thatβs how the pros do it.
If you just want to get shit done sure just reinstall and you are good to go, but I see these issues as a learning opportunity and I have tons of free time so I try and fix my system for hours on end. Also it rarely breaks so not much time is wasted.
Oh, for the days of constant distro-hopping ...
Do a snapshot and roll back. Actually faster and easier.
This was in the long long ago, grasshopper. We did bare metal installations back in the day.
BTRFS is your friend guys and gals βΊοΈ.
I switched to BTRFS recently, but found myself even more fucked when my system stopped working suddenly and I didn't know how to fix it without reformatting and installing grub again. Actually lost even more than I would have otherwise just because I wasn't knowledgeable enough to get any form of recovery to work. That first EndeavourOS install didn't last 2 months sadly.
Yep, everyone goes through that the first 2 or 3 installs, until you learn how CoW FSes work. It's not like anything else and it takes a while to master it, but once you learn how to use it, you don't reinstall ever again, just roll back snapshots π.
You give that up that strategy and lean into fixing shit when you put the time in to customize the OS and desktop/window manager experience... at that point you should understand your system well enough to make fixing it easier, and you are also afraid of having to redo some of your customization. That being said, you still should make regular system backups, especially if you are tinkering with the OS experience a lot.
If you are afraid of redoing your customizations you are using the wrong distro.
It's not about being afraid.
Customizing takes time and effort, which I'd rather use like.
Doing stuff?
Unless I want to re-customize it to be something else, I'd rather not re-make my entire set-up. I figured out what the relevant files were to how my whole set-up (DE look & behaviour, dotfiles for like fish
and nvim
) and copied it all to a USB Drive that I just drop onto my home folder whenever I install my OS on a new computer.
I still think that's a legitimate troubleshooting strategy. π