Terraform destroy
Terraform apply
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo
in Windows.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.
Terraform destroy
Terraform apply
This is how Tumbleweed cured my distrohopping—out-of-the-box Snapper meant painless rollbacks.
Press both
Hah. I'm sure once I read the rest of the responses I'll see the observation that 1 is just a slow route to 2
Reminds me of when I started using git lol.
*laughs in fedora atomic* debian could have a atomic version, ostree is distro agnostic
Debian is not a good distro for desktop usage. You cannot change my mind.
Can't change your mind? I'll just downvote you then :)
Button #3: Restore TimeShift snapshot.
Honestly kicking myself for not having this setup on my last Linux install
Good news is it's setup on my current install
Sometimes I learn my lessons the hard way... Multiple times.
1000% this. Just use BTRFS and avoid all the pain...
Linux is only free if your time has no value, and this is why.
I know it sounds counter intuitive but the way Debian handles things makes it really easy to break things and not know how. All these scripts that automate tasks it's easy to try to change something manually and have a script that automatically runs break something.
It would help if their wiki wasn't so painfully slow. How is it possible to have a website so slow it times out after like ten minutes of loading.
Second approach is better as it teaches you to fix and understand the system you're working with
Of course, this is a more complicated and energy - demanding approach, though. But if you wanna stay on Linux, you better figure such stuff out, this will be invaluable in the long run.
I should also mention that Debian, despite the Bookworm introducing more user-friendly options, is not a newbie-centered distribution and fixing things in there tend to be more tedious for an inexperienced user.
The upside, however, is that once you've set it up, everything will just work. But first you might face some pain.
I wish there was a way to see what the default values in a config file are for a given distro.
I'm guessing there probably is, and I just don't know it.
Maybe I should just make /
a git repo...
Don't modify the config in /etc/
, copy them in ~/.config/
and then modify them. You'll always be able to just look at the /etc/
for defaults.
Usually if its a boolean or nullable, a good config file will have a # uncommemt this line to enable this feature/disable this feature/bind to this IP address/give this thing a name
that is at least vaugely hints what the option does. But yes, its still fairly annoying.
You should check out the Fedora atomic distros if you haven't already. Making the system work more like a git repo is what they are doing with rpm-ostree. I am liking it a lot.
Without knowing a better way, my go-to solution woukd just be getting an full installation image and diffing my files with the files on it
I can't get sound to work probably on bookworm with an pretty old (10 yrs) system. It's so confusing between pipewire, pulseaudio and alsa.
Re-installs are for ~~scrubs~~ windows users. We don't do that here. SSH from other machine, chroot from live usb, switch to TTY or even UEFI interactive shell. Fix your shit, and get to understand how it works while at it.
Being able to do this is why Linux is so amazing. If Windows finds a corrupt file and can't repair itself, you gotta find the package it's part of (Windows update catalog), or create an ISO that's updated to do an offline repair. If the registry gets fucked, good luck fixing that.
Exactly! I rant about this a lot, but I know at least couple of people who run with laptops that have broken audio. As it turns out, installing sound card drivers is not really an option as the janky-ass drivers that the manufacturers put out nowadays can irreparably brick your entire system. It is beyond my understanding why recovery, restore, and even safe mode would even try to load them in the first place, but, apparently they do, and then crash before you could even do anything, leaving re-install as the only option.
Meanwhile, I rm -rf
-ed my /boot
directory the other day, and then df
-ed a couple gigs of /dev/zero
straight into /dev/sda
. Got it back up running in just a few hours... of kicking myself for why would I do such a stupid thing.
and then df-ed a couple gigs of /dev/zero straight into /dev/sda
do you mean dd ?
Oh yeah. Given how close the keys are together I might have tried to use dc
and ss
as well
Yes that's the "spend hours" part.