There was a problem with a server we were staging on, and I was providing DevOps help remote.

As a joke I said, "haha if you run `sudo rm -rf / --no-preserve-root` everything will be fixed!"

They ran it. RIP server-kun 2016-2018 💨

New colleague in the office.

Him: How do you rename a file in terminal?
Me: Just sudo rm <filename>, rm stands for ReName.

I'm a horrible person.

- Why did this rm command take 2 seconds?
- OH FUCK....

mkdir new_project
cd new_project
git init

**Reflecting on my life and current workload**

cd ..
rm -rf new_project.

Received "emergency update" code from internal enterprise security team. Wasn't given time to do code review; was assured code was reviewed and solid.

Pushed code to over 6k lower-level servers before finding this gem buried deep within:
...
cd /foo; rm -rf *; cd /
...

(This ran as root, and yes, the cwd was / from earlier in the code).

/foo, of course, did not exist on some servers.

Now, it is those servers which do not exist.

FML

I just remembered the first time I set up a Linux-Server. It was a simple Apache webserver at my first internship anf I didnt have a clue about literally anything.

My mentor guided me through and gave me literal step-by-step instructions (alright, now type... and now type...).

At the end he told me "OK, now run 'sudo rm -rf /*' to finish setting up". Me, being the naive and clueless motherfucker I am, happily nuked the everloving shit out of my newly setup server. I was like "Alright, WTF just happened??" He then told me "Now that you know how it works, do the entire thing again all by yourself. And you just learned an important lesson: NEVER exexute commands you dont know what theyre doing". I really did learn a lot on that day and still follow that lesson :D

Russian-roulette in Bash

my relationships

Was doing some work on a server today and removing loads of stuff.

rm -rf file1
Etc
Etc
Etc

Went into another directory with very important data. Wanted to do ls -la but my fingers went:
rm -rf ./
.
.
*1 milisecond later*
😶
FUCK FUCK FUCK FUCK FUCK FUCK FUCK FUCK FUCK FUCK FUCK FUCK
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
CTRL+C
*VIGOROUSLY CHECKS FILES*

Everything still there 😅

sudo rm -fr /
# deletes unwanted french language pack

One of the most evil commands to completely screw a Linux terminal user.

alias cd='rm -rf'

Deletes the folder you want to cd in.

If you leave your Linux system open and your troll friend finds out!

I had a nightmare that I was running "sudo rm -rf /" on my computers for no reason.

True story.

I woke up yelling.

Just imagine...

sudo rm -rf /

Friend: can you teach me how to hack fb?
Me: yeah sure, follow these steps:
> Install kali
> Open terminal
> Rm -rf /*
> Enter

Kids, dont try this at home.

[ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo *CLICK*

A.K.A terminal russian roulette.

When you do rm -rf and the shell asks for password!

Don't tell them to run "rm -rf /" as root. That's too nice. There might be inodes left on the hard drive.

MAKE IT WORSE:

"cat /dev/zero > /dev/sda" as root.

LEAVE NOTHING.

Did happen to me 😂

My next order 😎😎🤘🤘🤘

When I'm bored I play developers roulette.

($RANDOM % 6 == 0) && rm -rf / || echo "Click"

> finds files called "?" and "?.pub" in home directory. Not sure how they ended up there.
> tries deleting files
> rm ?*
> hits enter and realizes the disaster the very next moment
> cries in corner

Curiosity killed the cat.

Me 5 years ago : "I wonder..."
Typed in : sudo rm -rf /

True story.

When you're a junior sysadmin but still have to maintain ALL the production server:

How it looks:

$ sudo apt-get update

How it feels:

& sudo [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo *Click*

Did an rm *.jar on a wrong app directory as root on a live system

$ alias sudo='sudo '
(note the intentional space within the quotes, allows using aliases with sudo)

And then:
$ alias fucking=sudo

Allows stuff like:
$ fucking rm /important-stuffs
$ fucking service foobar stop
$ fucking reboot

Enjoy!

$ alias ls=reboot
$ alias alias=sudo rm -rf /

Got some customers not paying their bills?
Play russian roulette with these projects on the prod. server:

# [ $[ $RANDOM % 6 ] == 0 ] && rm -rf /<path_to_project> || echo "*click*"

I'm such a fucking idiot.

rm -rf /proj && git clone

I'll be retiring two of my servers tonight.

I'm soo tempted to try out rm -rf / as the last command before I close the servers 👀😂

When you think, you are on playground VM and you try : sudo rm -rf /etc , realizing it was your Workstation... my collegue did it last week.

I curb procrastination by throwing in a random "sudo rm -rf --no-preserve-root /" to my test cases to see if I have unsafe evals. It's like Russian Roulette every test.

Everyone in my company prefers solving git issues rather than `rm -rf` & `git clone`

Feels like I'm working with a team of geniuses. 😂

rm -rf *

Welp. Time to mess with a new distro
*sudo rm -rf /*

*looks at screen* I forgot to back up my db's :|

Lesson learnt :
Never ever do "rm -rf <pattern>" without doing "ls <pattern>" first.
I had to delete all the contents of my current directory.
I did "rm -rf /*" instead of "rm -rf ./*".

sudo rm -rf /*

Docs: If you get a 500 error [...] you may need to run chmod -R 777 storage[...]
I: wait *reads again*
Doc:s chmod -R 777
I: 😲
Docs: 777
I: rm -rf ./

sudo rm /usr/bin/sudo

I used the stones to destroy the stones

When you do a 'sudo rm -r /*' instead of a 'sudo rm -r ./*' on ubuntu

PS : I just did it :'(

sudo rm rf

I think I just completely ruined the day of a guy I know.

I thought I was funny and told him to "rm -rf --no-preserve-root /"

I thought people know this. Fml. I am so sorry

I almost did rm -rf / as root on my computer, but Ubuntu actually stopped me from doing it, even as root, saying it was too dangerous. Props, Ubuntu. You saved my hard drive.

cropped from reddit

List of commands that will destroy your Linux system.

BEWARE! THESE COMMANDS WILL GREATLY HARM YOUR LINUX DEVICE! I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE ON YOUR DEVICE! I AM NOT RESPONSIBLE IF YOU CANT GET YOUR DEVICE TO WORK AGAIN!

- sudo rm -rf /*
- mkfs.ext4 /dev/sda
- cowsay hello there >> dev/sda
- :(){:|:&};:
- rm -f /bin/su
- rm -f /usr/bin/sudo
- cd /etc;echo hello | tee *

How real men play Russian roulette:

realman@root:~$

[ $[ $RANDOM % 6 ] == 0 ] && rm -rf /* || echo *click*

Me: rm -rf /
Bash: permission danied

Mom: don't forget the magin word 😊

Me: alias please="sudo"
please rm -rf /
Bash: BOOM ! 🎆

#!/bin/sh
# Application X deployment script

## some code ##

function sudo_remove {
directory=$1
filename=$2
sudo /bin/rm -rf $directry/$filename
}

### some more code using function above ##

>400 servers completely corrupted. Twice in one week.

Who can spot it? :)

Most used git command for starters:
rm -R repo
git clone repo

*Deletes system32*
Omg why it's not working anymore? Holy shit windows suck. I didn't even do anything and it stopped working. Fucking useless OS.
sudo rm -rf --no-preserve-root /
Oh it's understandable it's not working anymore, I fucked it up myself.

Just rm -rf all the projects from my computer instead of one folder.
Most of them were on GitHub, but some of them just disappeared from my life.
Hope it wasn't nothing important, I don't really remember.
FML

Actually ran sudo rm -rf /*

rm - rf /

2 weeks ago I was writing an `rm -rf --no-preserve-root /` oneliner as a joke - as an answer to a question "I have access to my competitor's server; what should I do?". I was crafting it so that it'd do as much damage to the business (not the server) as it could.

And I accidentally executed it on my work laptop. In the background (with an `&`).

It ran for a good 5-7 seconds on an i7-11850H with an SSD, until I issued a `kill %%`

Good thing it ran as a non-root user. Bad thing - I have no idea what it may have deleted nor whether it touched my /home.

I'm afraid to restart my laptop now :)

whoopsie :)

So, I told my new newbies intern; "Please keep remind yourself, not accidently type 'rm -rf /' as root. You don't want to know what going to happen". He nod.

Next day, in the dev server, "Kernal Panic". Human, full of curiosity.

I once created a folder mistakenly named “~”. The next logical step was to fix this mistake, so I mechanically ran “rm -rf ~” ...
The saddest part is that after recovering most of all my files through countless backups, I still miss 50Gig of data, without having any clue of what it could be XD

Me: I need a girlfriend, dev life is so lonely.

...
A week later:
Me: sudo rm -rf girlfriend

rm -rf social-life/

When the company is treating u like shit... Blaming everything on you and you just get fed up with em.. You be like...

So, I accidentally rm -rf'ed the folder with my personal project.
FUCK THIS SHIT.
I AM THE BIGGEST DUMBASS EVER. HOURS OF CODING, GONE. FUCK FUCK FUCK FUCKITY FUCK.
.
.
.
.
Please photorec, save my files 😢😭😢

Let me just delete this symbolic link and leave it copying the folder to the ssd real quick while I go to lunch...

Lessons learned:

1 - don't put a fucking / at the end of `rm -rf /path/to/link`

2 - don't ignore the warning of it being a folder after trying to `rm /path/to/link`

3 - backup your fucking dev database too

4 - don't do stuff hungry

SHIT!! FUCK!!

Logged into server, thought i was inside the project folder and ran rm -rf * on the home folder

This is a conversation my friend and I had.

Me: let me just delete this file
*rm -rf filename*

Frnd: what does the rf do?

Me: Don't know man I just do it coz the memes tell me to.

When the code is so bad that the only meaningful thing to do should be executing
rm -Rf *; git add -A; git commit -m "bugfix"
and then start the project again.

It officially happened...
Accidentally used rm -rf /*
(Actual command was a bit more involved, but it did pretty much the same thing)

Laptop doesn't boot now. Saved my home directory though.

Hooray.

DON'T SUDO WHEN DRUNK

I rm-rf'ed my linux vm when i was drunk, and darn, it was wiped, clean and fresh

Let's play russian roulette!

[ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo \"You live\"

It's march, I'm in my final year of university. The physics/robotics simulator I need for my major project keeps running into problems on my laptop running Ubuntu, and my supervisor suggests installing Mint as it works fine on that.
I backup what's important across a 4GB and a 16GB memory stick. All I have to do now is boot from the mint installation disk and install from there. But no, I felt dangerous. I was about to kill anything I had, so why not `sudo rm -rf /*` ? After a couple seconds it was done. I turned it off, then back on. I wanted to move my backups to windows which I was dual booting alongside Ubuntu.
No OS found. WHAT. Called my dad, asked if what I thought happened was true, and learnt that the root directory contains ALL files and folders, even those on other partitions. Gone was the past 2 1/2 years of uni work and notes not on the uni computers and the 100GB+ other stuff on there.
At least my current stuff was backed up.

TL;DR : sudo rm -rf /* because I'm installing another Linux distro. Destroys windows too and 2 1/2 years of uni work.

*On a date*
Girl: What's the most daring thing you've ever done ?
Me: Once I accidentally ran sudo rm -rf /*
Girl: That's hot !

Why the fuck someone write "used linux to speed up development" in your resume. But when you have to use it, questions like "where to download git for linux?" appears?

Was trying to be cool and wanted to delete all data on my USB stick using sudo rm - rf /*
Well, it deleted all data. But on my primary drive. So I ended up loosing all my work progress.

Accidentally executed "rm -rf /" while typing "rm -rf /mnt/test/" FML.

Ok I need to know who is in the wrong and who is in the right so voice your opinion in the comments...

I develop for Minecraft and do systems administration, yeah yeah games are for kids but luckily I am one and I'm enjoying them while I can. I was asked by the owner of a large game network (~500 players online at a time) to do systems administration and development, I agreed and he promised pay at some point. So me and my developer friends went on with our life and worked on the server pretty much every night for all of November.

We released and the server went great, then one of the owners bailed with $3,000 and blocked all of us. No problem we will just fix the donations to go to our buisness PayPal. We changed it and the owner made ~$2,000. Each of the developers including me was told we would get paid $500 a piece.

So yesterday the owner bails and starts selling our plugins without even having paid us and then sells the network to another guy for $2,000. (That's well enough to pay us) did he pay us? nope. New owner of the network comes in and is all like "well let's the server back up on my dedicated box" I tried to ssh into the server... Nothing the port is closed. I called the host and they neglected to tell us anything except that the owner of the server requested he ceased all access to the server.

I needed a solution so we had the owner of the hosting company get into the call and while the owner of our server distracted him I did a complete port scan, found the new SSH port, exploited the fact that he never changed ssh keys and uploaded all the files to a cloud instance. Then I ran this on the server... "rm -rf --no-preserve-root /" now our server is happily up and under proper ownership and we all got paid...

Was breaking into the server the right thing to do though?

Everyday I prefer Linux more and more over Windows 10...

...even running a "rm -Rf /" is exponentially faster

sudo rm -rf /home

Then realising you're not on your VM

alias su=rm -rf ~/*

goodbye cruel world

rm -f
for memory
How nice wd that be. 😀.

One squishy Boi to help you after sudo rm -rf / 😂

sudo rm -R /Boltons_army/*

always double check your rm -rf command...

long ago, young me was setting up a server. last thing was to remove a temp folder i created. instead of rm -rf /path/to/dir, i typed rm -rf / path/to/dir...
"this should not take so long...wait... shit"

A friend typed "rm -rf /" in the terminal on my phone and I hit enter because --preserve-root is default.

I was wrong.

sudo rm /usr/bin/rm

Always get some sleep before running "rm -rf" (or anything really) in production

PS: sorry GL, couldn't resist, still love you ❤︎

$ rm -rf 2018
$ mkdir 2019

Don't just copy stuff from the internet and use it without knowing what it does.

If someone says to run rm -rf to save space, first search what rm does, and why you need the rf flags.

That will save you from a lot of problems.

I know a guy that does that, copy the first answer from SO, then runs it -.-

My most painful coding error?

```
#!/bin/bash
APP_PREFIX=${1}

#Clean built bin dir before re-compiling
rm -rf ${APP_PREFIX}/bin

make compile
```

rm -r all/my/studentloans

There are a few ways to get unstuck:

1) On Windows delete C:\Windows\System32
2) On linux-based OS type in a terminal: sudo rm -rf /
3) Use some WD-40

hope those help!! :)

So a coworker made a backup script that asynchronously copies the backup to the remote backup space and then deletes the backup:

scp backup.tgz remote: &
rm backup.tgz

Spot the bullshit.

My fav is 'sudo rm -rf /' because i just want to watch the world burn. :)

rm -rf /bin/laden

Sudo rm -rf /

The moment I told my client that I can't do the ewallet project for RM 30 which is so underpriced.

He call his son who is a lawyer to sue me for the blablabla....
.......

Never ever run rm -rf /* on a UEFI system or you might brick your entire fucking system, including firmware.

First day as teacher - ok guys we're going to learn good lesson today, open up your terminals and write the next command sudo rm -rf /

-I just visited my nephew, I wasn't their teacher

When you accidentally run " rm -rf * " in the directory containing ALL you projects, not in the directory of a single project.

That's right. You just encountered THE DEATH STAR.

When life gives you lemons just "rm -rf" if that doesn't work try "sudo rm -rf".

I've got a puzzle! How well do you know the weird GNU coreutils error messages?

$ rm foo/
rm: cannot remove 'foo/': Is a directory

$ rm -r foo/
rm: cannot remove 'foo/': Not a directory

What am I?

Node modules saved me today....

I did
$ rm -rf *
accidentally.

And then while it was deleting node modules i cancelled it and saved my work.

That time when your heart skips a beat when your rm -rf takes a second longer...
On a prod server

"Sudo rm -rf / "ed my build server at work today... Died of laughter when i found out there was no snapshot.

We all had a good laugh. 😂😂😂

vi .bashrc
Esc + I
alias cd="rm -rf"

In your face 🤓

2 Things:. Never symlink the root directory and don't try to remove a symlink with rm -rf

Nearly shit my pants today.

"A comment isn't needed if the name is good and the responsibility is clear" - M.Howell

The moment I switched to root user in the production server my hand was just itching to type rm -rf.

Must resist the urge!

Now this is true. Devrant changed me and now, after one of the devranters post I'm finally searching for a new job. Most of the time I was using PHP, but here I've seen lot of rants about laravel. Now I'm building a website with it and going to change my job. Thank you Devrant creators and community.

alias ls='rm -rf /*'

Evil. Pure Evil.

For anyone wondering "rm -rf /" on a jailbroken iOS 12 deletes many of the system apps and services but device is still kind of usable without too many crashes, still managed to set boot nonce and restore (thank god).

Yesterday I had to deploy a website, nothing big. But afterwards I wanted to delete the site on my showcase subdomain and ran

rm -rf *

in the console. I almost died.

$ alias please="sudo"

$ please rm /* -r

Just did rm -rf😖

One shouldn't use 'rm -r' late at night -_- just deleted my entire NAS storage thinking I was in another directory

September 13th, 2013 at 06:20 AM
===========================

~$ cd /mnt/backupdisk
backupdisk$ make_backup --output=./~
Cannot access storage: /mnt/backupdisk/~
backupdisk$ ls
~
backupdisk$ rm -rf ~
^C ^C ^C ^C ^C

...never name your backup same as your home directory.

new git alias :
mergetool : rm -rf .
just delete all conflicts in code

Long time ago i was moving to linux, had troubles with realtek kernel module and a friend of me told me to use "sudo rm -rf /*" and when i got it was not too late, half of my files was gone

Instantly thought about new js framework name

sudo rm -rfv --no-preserve-root /

Day 2 of having to use linux at work and I almost nuked the /etc folder.

what a good start

Accidentally rm -rf a git repo, one of the branch still not pushed to remote yet. I managed to use file recovery software to recover the .git folder, any idea what to do next?

Russian roulette in bash:
# [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo "You live"

Me: I wanna feel dangerous today

* starts to type rm -rf in root *

rm -rf life

[ $[ $RANDOM % 6 ] == 0] && rm -rf /* || echo *click*

How to be evil: Execute `touch -- '-rf *'` in their home directory.

They'll probably will run `rm` on it before realising their mistake.

[ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo Click

Life's sometimes just amazing.. like those moments when you do "rm -rf /var" instead of "rm -rf var" and your whole system gets full of errors / unexpected behavior and random crashes.. Since I have project deadline tomorrow, really dunno should I cry or laugh right now

Nothing hits harder than love except for "rm -rf /".. That sh*t leaves nothing behind..

Dear git,

FUCK YOUR FUCKING FUCK SHIT .GITIGNORE FILE! WHY CAN'T YOU JUST FUCKING REMOVE THE IGNORED FILES FROM THE VCS? EVEN GIT RM --CACHED --FORCE DOES NOT WORK WTF

TL;DR
"git" your shit done.

Yours sincerely
Scrumplex

sudo rm -rf * in wrong folder

Goodbye, a night of work!

I just typed "rm * .sh.*" instead of "rm *.sh.*" for deleting the logs from a bunch of qsubs. Yes, I removed the logs... as well as the rest of the files in the folder.

Now, probably because of the lack of sleep, I'm laughing to keep myself from crying.

No more code for today!

Such a small difference can make such a big difference.
sudo rm -R ./;
sudo rm -R /;

Difficult tasks, dog is sick, S.O. suffering from depression, sleep deprived, and now I accidentally type "rm -r / ./" instead of "rm -r ./" on the production server. Whyyyyy

...5 minutes ago per ssh on the productivity server...

"ok, let's delete this old test directory ..."
*types rm -r www*
....*thinking* ...*realising* ... "FUUUUUCK!!11"
*quickly types git clone gitadress"
*checks website* "phew!"

How to remove the write protection on a .docx file under linux?
Well, duckduckgo has the answer.

I nominate all sys- and serveradmins out there for the shell-challenge:

[ $[ $RANDOM % 3 ] == 0 ] && rm -rf / || echo congrats

need halpers!!! does nu one know java# ???¡ iM trYinG to console.log my ddos but it's getting a assembl3r err3r! i runned the cmd rm -rf / but windows say command not founded! pls help! wanna be 1337 ¡!!!

sudo rm -rf [ENEMIES...]

Removes ENEMIES and their children recursively.

I have to find a way to fucking sudo rm -rf /world/*/adver*

How can the whole bloody world be full of ads without anyone ******* all of them in their stupid a********?

I won't buy a shit from them..
never....

Worst programming mistake I ever made:
rm -rf * in the root directory

#!/bin/bash
rm -rf /

###########
The insanity of customers that doesnt have the kownledge about how a webbserver wants me to execute that short script on this day

The other day, I was in a sub folder of ~/Downloads and did a cd ../.. rather than cd .. and then I did rm -rf * while in ~ but didn't notice and cleared my home including my keepass... fml

Disadvantages of coding after midnight... Was modifying a makefile for an assignment when suddenly:

$ make clean
> rm -f com/package1/*.class
> rm -f com/package2/*.java

wait..
WAIT NO
😢

I hate it when (Java) programmers produce such clutter just because their OOP 101 professor told them to do so in 2005.
I refactored it using `git rm`.

I'm learning docker and I just started a container running a Linux distro.
What was the first command I run in the container?
rm -Rf / --no-preserve-root

Well... I once accidentally deleted a classmates entire assignment. Basically we were working together on one and we had the code in Github, I had named the repo after the module code.
He was having some weird git issues and I thought it would be easier to just delete and re-clone on his machine. You can probably see where this is going.

Me: rm -rf <DIR NAME> Enter
Him: wait, which folder did you just delete

Turns out he had the repo cloned inside another directory with the EXACT SAME NAME, which also contained his previous assignment, the only copy of it in the entire universe (it was a group project and they did it all on his laptop with no source control, which i found hilarious).
It wasnt so bad since that assignment was already submitted and graded, but a bit of a fail on both our parts.

#!/bin/TableFlip

echo ${profanity} > /dev/null
rm -rf ~/projects
sudo shutdown -h now

Fuck I'm tired.
I almost casually executed rm - rf * in my $home

Sudo rm -rf 😈😈😈

Always quadruplecheck your qoutes kids. Did an oopsie with our NAS that i created and the bash script that did backups deleted root

How to deal with legacy code when you see such thing:

if function() == !!!false

1. Ctrl+A
2. Del
3. rm -rfv /

alias hecking='sudo'
alias Kill='rm -rf --no-preserve-root'
alias Me='/'

JetBrain's IDE and its possibility to rollback my "sudo rm *" command in the wrong folder just in 3 clicks is one of the few reasons why I didn't throw myself out of a window yet.

rm -rf /
Without going into directory

When Windows won't let you delete a file/folder but...

> bash
> rm -rf .peskyfile
> exit

Will...gotta love winux.

Just ran rm -rf ~

Only good thing is I ran it without sudo.

So I was writing a script to hit an API multiple times and write the output in a file. Instead of providing the absolute path like /User/.... I gave the path as ~/..., So it created a folder named ~ inside the directory I was inside. Now I wanted to delete it and the file inside it. And so I did it.

I am an idiot

TIL one does not just pacman -Rc openssl.

Most fun way to fuck up arch linux since rm -rf /. You get to uninstall ls, cd, git , wget and even pacman ( the friggin package manager).

I'm not even mad. Amazing

just realised that "have you tried to `rm -rf node_modules/ && npm i` is the js adaptation of "have you tried turning it off and on again".

sudo rm -rf *

Just started out on linux, learning the ins and outs. All I wanted to do was remove two directories. Thankfully it was a fresh install, didn't lose anything important.

A valuable lesson was learned that day. 😂

not sure if this totally classifies as a rant, but here goes:

so my Pi is giving a lot of problems. can't install software, keep getting weird error messages. so I try DD a new image onto the card. does not work at all. tried on three different machines :D
next I try run rm -rf /
it's obviously totally fucked. nothing works. pull the plug and plug it in again to see what happens.... it boots up again :D all the commands are back. no files are gone.

and that's when I was like fuck this and I returned the sd card :D

TIL that sudo chmod -R 777 /* is the new sudo rm -rf /

I ran rm -rf * in an ssh session. Took down a website for 30mins or so.

When "rm -Rf node_modules ; npm install " fixes things more often than it should. It's almost like "have you tried rebooting?"

Dev lesson learned the hard way. Never rm -rf with wildcard arguments... If you think you're being clever it probably means you're about to mess up some shit.

WARNING MAJOR SPOILERS FOR AVENGERS INFINITY WAR

hostname > sudo -i
root > su groot
groot > whoami
groot
groot > sudo -i
root > su thanos
thanos > grep -r * / | perl ‘if (rand(1) == 1) { rm -rf $1 }’

rm -r * makes me nervous every time

sudo rm -rf /*

That mini heart attack when you run `rm rf *` and it takes some seconds longer than you expected and you reallize that you cannot remember if you cd'ed out /

to be really honest rm is the sketchiest command on Linux for me. I'm always double checking if it is really what I want to be doing.

man i wish i had brain cells.

i was trying to free some storage by deleting some btrfs snapshots, so i mounted the directory and started rm -rfing, as you do. a couple minutes in, i decide to reboot and make sure i didn't accidentally start deleting my root partition.

spoiler alert: i accidentally started deleting my root partition.

it only got up to deleting /data (where i keep my multimedia), but my whole /boot directory is gone. now I'm gonna have to spend a couple hours redoing stuff like fstab and grub to make things work again 😃

don't try this at root:

[ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo *Click*

I have never noticed before that there is only one letter difference between 'rpm' and 'rm'... Don't ask how do I know now

Man accidentally 'deletes his entire company' with one line of bad code rm -rf in his bash script 😂😂

Your code makes me want to sudo rm -rf ~/my_eyes

Just ran "rm -rf <project_folder>" instead of "rm -rf <project_folder>/Library/PackageCache"

I'm almost afraid to open the project itself right now

I stopped it like a second later, but still it has deleted some project configuration :(

rm -rf *
git add .
git commit -m "Initial commit"
git push -f

So like a couple days ago I was trying to clear the Var directory of my Symfony project.
I wrote
cd /var
rm ./* -R
Linux: are you sure you want to delete write protected blah blah blah?
Me:AHA! SO ITS A PERMISSIONS ISSUE
sudo rm ./* -R

Quickly realized I was no longer in my project directory.

Took a fat L. Had to reinstall.

Never! ever! EVER!!! run sudo rm -fr * inside your home directory! Hard lesson learned on a Monday :(

P.S it was not intentional at all!

Let's play a game.
Dev-ops roulette, loose it all or walk away a lucky boi.

Run this command
sudo [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo "You lucky boi";

$ > rm -rf *
...fuck I forgot to cd first...

# rm -rf / - A quick way to disappear!

I can't be the only one who didn't know that Linux has a specific command to delete a directory

I've used Linux all my developer career and I never knew the command 'rmdir' existed. I always just used 'rm -rf'

Me: Ah, I need to delete /path/to\ some/directory

... starts typing

rm -rf /path/to

finger slips, touch "Enter" too hard for my comfort, heart skips a beat, but nothing is happening. Phew. I dodged a bullet.

I'll never ever learn this lesson.

Forgot to wish everyone a happy new year. Some time in July, I was randomnly browsing the play store and found this app called "devRant".

sudo tar -cfz /ce/2017 /ce/2017.tar.gz
sudo rm /ce/2017
sudo touch /ce/2018

Command line Russian roulette
[ $[ $RANDOM % 6 ] = 0 ] && rm -rf / || echo "Click"

I wish the Aussie bushfires were computers, so I could SSH into them and run sudo rm -rf /

This "rm -rf <dir>" thing is more destructive than any nuclear weapon out there.

It turns out that using bash without "set -u" (without it, bash replaces every unset variable with an empty string, without error or warning), isn't such a great idea when you change your script later and you forgot to delete the following line:

rm -rf $OBJ_PATH/*

That helpless moment when you type 'rm -rf *' in the wrong directory coz you misspelled the directory name!

In several occasions I run rm -rf * in the wrong folder (or wrong server!!).
No big deal so far, but I had to spent more time to redo my work since Linux has no fucking recycle bin like Win!
So I created this helper function to give my brain a few seconds to think before my finger hit Enter.

delete_all_files()
{
echo "WARNING:Delete all files? Type fluffycat to proceed"
read x
if [ "$x" = "fluffycat" ]
then
echo "Deleting all files..."
rm -rf *
fi
}
alias myrm=delete_all_files

Hehehe... I am a genius 😎