Timeline for How to use rm in an answer
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:14 | history | edited | CommunityBot |
replaced http://serverfault.com/ with https://serverfault.com/
|
|
| Mar 20, 2017 at 10:18 | history | edited | CommunityBot |
replaced http://superuser.com/ with https://superuser.com/
|
|
| Oct 28, 2016 at 9:12 | history | edited | user | CC BY-SA 3.0 |
Incorporate from comments
|
| Oct 22, 2016 at 17:34 | comment | added | kasperd |
Reminds me of a comment asking: How do you even type --no-preserve-root accidentally?
|
|
| Oct 22, 2016 at 9:52 | comment | added | Qix - MONICA WAS MISTREATED | Btw, this is what accidentally their own system means for those not accustomed to the meme. | |
| Oct 22, 2016 at 8:19 | comment | added | Danra | The guy in the third link you've attached wasn't saved by the safeguards :( although he also made use of an asterisk. In any case, the point was just that non-technical users don't want to do anything bad as your analogy suggests, just that they might do so by accident. | |
| Oct 22, 2016 at 7:59 | comment | added | Journeyman Geek Mod | Oh, it quite literally is more difficult than that to rm -rf / - see my first link. You literally need to explicitly tell it to delete the root directory of a system | |
| Oct 22, 2016 at 7:57 | comment | added | Danra | "if someone wants to break open the gun locker" - a better analogy for telling non-technical users to use "sudo rm" is handing them a gun and telling them to use it, without having passed any weapons handling training to make sure they don't shoot themselves in the foot by mistake. | |
| Oct 22, 2016 at 7:50 | history | edited | Journeyman GeekMod | CC BY-SA 3.0 |
added 24 characters in body
|
| Oct 22, 2016 at 7:27 | history | answered | Journeyman GeekMod | CC BY-SA 3.0 |