The heart skip when an rm command runs longer than expected.
Why does it always take so lang to remove the french language pack???
that really is a terrifying feeling
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/binHow do I stop some big mean missed command from tearing up my main drive?
The answer: Use Ctrl-C. And if that don’t work, use more Ctrl-C.
And if that don’t work? Use Ctrl-Z.
Use Ctrl-Z
followed by
jobs,kill %1, etc
“The right command in the wrong directory can make all the difference in the world. So rise and shine, Mr. Tux. Wake up, and check the log files…”
kkzzt Pick up that coredump.
I heard this in G-man’s voice from the first two or three words!
That was intentional :)
Apart from the initial “Rise and Shine” before the first sentence, this is a direct play on G-man’s intro speech from HL2.
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
sudo kmsLast 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…
Made that mistake last week. Luckily it was just a chmod and not a rm. Stomach did a flip regardless.
oh i made that same mistake a month ago when trying to chmod 777 -R another partition… and ran it in / instead
when I was but a baby sysadmin, my boss did that to a production server
Luckily it was just a chmod
that can still render a system unbootable 😅
Hah, fair enough!
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~…This is why i find rmdir useful.
after mistakenly creating a directory caller ~…
How do you even delete such a directory?
rmdir ./~
That makes sense.
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
