ctrl-c ctrl-c ctrl-c ctrl-c ctrl-c
i ctrl+c my fucking face off when that happens.
oh and in case y’all can’t read it, the command is
cat *in/bin
Btrfs snapshots to the rescue!
I’ve been meaning to tinker with Brfs. Is the idea that snapshots live on a separate volume so you can always recover a messed up system?
Last week “I was trying to fix something” and made some bad decisions. Long story short, wrong command in the right directory the screen flashed like in this meme💀. Well, I liveUSB to reinstall the whole thing. Then I remembered that I installed Cachy with BTRFS snapshots. Bam Fucking magic, it’s like nothing happened… I call it the Ohh shit, Ctrl-Z OS troubleshooter. Yep I’m new in linux…
When I paste a 250k-line log to console.
wondering why firefox hangs as you paste a 30MB text file into an online diff tool
rm -rf is always right. No matter where. Supposed, of course, you are root.
No discussion. I am root! I am always right!
Made that mistake last week. Luckily it was just a chmod and not a rm. Stomach did a flip regardless.
I was trying to sudo rm -rf ./ Once and missed the / so I just used rm -rf . And this was before they added --no-preserve-root as a default so it just ripped through my entire drive.
sudo rm -rf ./andsudo rm -rf .are, as far as I know, the same command. Did you mean that you dropped the . and ransudo rm -rf /?Fortunately for me, this never happened to me, but I have gotten pretty close to running
rm -rf ~after mistakenly creating a directory caller~…after mistakenly creating a directory caller ~…
How do you even delete such a directory?
rmdir ./~
That makes sense.
When I paste a 250k-line log to console.
I’ve aliases sudo rm to sudo rm -i
I recently noticed that the logging framework I use does not limit the log’s length. I don’t know how exactly I filled the memory so quickly, but I did
