Dumb and Dangerous Unix Commands You Should Never RunEver used a Linux computer system? If so, you will undoubtedly have come round to configuring your computer, and its files and software, using a Unix terminal. If you are new to this, it will take practice, but I promise you that you will be fine as long as you don't run any of the commands specified in this list, as there are commands out there which can create serious and irreversible problems with your computer. For that reason, I strongly advise that you take care with your Unix usage, and absolutely, 100%, do NOT run any of these commands. You have been warned.
The classic hard disk killer. This forcefully and recursively deletes your entire drive, including config files, boot files, and doing profound, irrefutable damage to your computer and even removable drives. Just don't.
The null directory is a system directory in which files transferred to it are automatically deleted. Several commands direct temporary objects here, but what this will do is dump the entire root directory to the null directory, and all of it will be gone for good.
This deletes the boot files from your computer, and so you will be completely unable to turn it on!
This rewrites the output of the given command to your system hard drive, erasing everything that was there!
Got data on your hard drive? Of course you do, and it's important to keep your computer running! This will replace all of it with zeros! Those crucial objects keeping your computer alive have been replaced with junk!
This is known as a fork bomb command. Running it once will continually replicate itself until your processor is overwhelmed, likely leading to widespread data corruption.
This is the equivalent of formatting your hard drive. It makes a new hard drive ID, but in the same location as the one you are running, therefore you'll erase your drive entirely by doing this.
This will download the software from the specified URL and automatically execute it. If the software is malicious, it could mean you just killed your computer.
This is something used commonly, however very carefully, to fix mistakes in previous commands. The danger is that if the correction contains malicious content it will automatically be run when substituted into the previous command.
If this is commonly used then it seems strange to have it on a list of commands you should never use. Maybe a better term would be never use if like me you are not an expert on computers.
If multiple users work on your computer, this will instantly allow them to see, edit, move and delete anything and everything previously restricted.
Nothing like wiping your root folder whenever you want to view the contents of your working directory.