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.
I accidentally untarred archive intended to be extracted in root directory, which among others included some files for /etc directory.
I went on to rm -rv ~/etc, but I quickly typed rm -rv /etc instead, and hit enter, while using a root account.
I've had a combination of tab complete and filename spaces lead to things like rm Some\ Common\ Prefix * at least three times. Instant regret. I've now got a pretty good intuitive reflex around this type of thing. You eventually get enough callouses.
Ah, this is why I set up snapper on my btrfs system
TIL rm -v is a thing
For when you want to livestream your failures directly to the terminal
Rest in peace my granny,she got hit by a bazooka
(got no clue why, but really FEELS like an appropirate reaction to have, I salute to you and your pain sir!)
Make an alias in .bashrc (or equivalent) so that rm always have the -i flag to prompt for βyou really wanna do it !?β.
This is one thing that I hope never happens on my system....
Well at least you got to watch
You use btrfs, right? Right???
Tried the terminal emulator for the first time today, but I kinda can not get used to the fact, that I cannot move it around :(
Ah! thx for reminding me to setup timeshift again on my new system :)
Why is the cursor still on the same line as the prompt?
shh enjoy the funny /s
I've literally done rm -rf / while root. I thought I was elsewhere and did rm -rf . and I was in the top level directory. When it took way longer than I expected, I hit CTRL+C about 10 times and looked at the damage. Oops.
Luckily it didn't get to /home, but it did wipe out /bin and /etc. I had to rebuild the OS. I learned.
Half a year ago I accidentally git cloned to a folder named ~, so naturally I did rm -rf ~.
Mistakes were made. Fortunately I backup my ~ so it was just annoying.
If I'm about to run an rm with a slash in it, alarm bells go off in my head. I prefer to cd to the parent and then rm whatever without slashes in the name.
That didn't save me the other day when I accidentally put a space before an asterisk, but thankfully that wasn't in a place that was overly important.
Gotta retrain myself to look out for extra nothing now.
I chowned root recursively once to root:root caught it half way when errors started popping up about stuff that was denied. Was trying to do ./ but missed the .