lol sudo rm -rf /
lol sudo rm -rf /
Also it’s just wrong advice, since you explicitly need –no-preserve-root for it to work… /s
Jokes aside, please don’t troll anyone with things, that can have severe consequences. Yes, they should have a backup. Yes, they should know how to restore from it. Yes, they should have tested it prior. Yes, you shouldn’t blindly trust people online.
But even then: Assuming my backup works and I can easily revert the damage. Maybe I need to complete an assignment until tomorrow and just lost 1-2 hours because my PC was busy doing the restore? There’s always a high chance of collateral damage
Sudo dd if=/dev/random of=/dev/* will fix your disk
Sudo: command not found
–no-preserve-rootif you use /*
Some people are really bad at empathy. They don’t actually, like, imagine the pain and confusion in the other person if they did unwittingly damage their computer. They’re thoughtless. That’s a lot of words to say “They’re kind of stupid.”
And some people do imagine the pain of the victim, and do it anyway. Those people should probably be on a watch list before they start killing small animals or shooting up a school.
Having moderated forums back in the day, I can answer to some of that motivation.
First, some people are just bullies. A sense of tribalism forms around bullies, who feel the need to act out and repeat the abuses they have endured. Hazing stems from this, too. Cruelty masked as “you should know better,” advice. Given too late.
Some have a smug sense of superiority, and want to keep it that way. Less smart people means they stay king of the mountain. Others are scared their own lack of knowledge will cripple them if they don’t keep the potential competition down. Insecurities drown out any sense of empathy.
Some people hate themselves so they punish others in retaliation. Like, trying to erase past cringe by making others hurt to even the score.
A few are sick of “the same fucking newbie questions again and again and again,” but still hang out in newbie forums for some reason.
:(){:|:&};:
shoutout to @[email protected] who (i believe?) created this fork bomb :)
there is a great in-depth writeup about fork bombs in general, and this one specifically, here.
rm -rf ./*. The mistake being that I (more than once…) accidentally put a space between the . and /.
-rf / cases, so that’s less likely to happen anymore. Still not a bad habit to use ls though
/*. gp was totally screwed with their typo.
This is the best advice in the whole thread.
Check what you’re doing before you do it.
I forced myself to use trash (from trash-cli) when I lost my first server install from this.
Nowadays, I’ve removed the alias from rm that asked me to use trash, and am still using trash if there’s a chance I might want to keep something.
\rm
rm -rf removes only the République française language pack
honestly I’ve had the best luck when I use the French Riviera version to delete my hard drive:
rm -Riv /
rm -fr /*
command -v lol is returning an error on my system???
Ok now type “touch /this”
And then hum the famous M C Hammer song.
that being said… what’s a good website i can at least go to and learn some linux basics and progress to more advanced stuff? i’d at least want to check that out before i start bugging people…
i had the opportunity to take a class back in college but 18 yr old me couldn’t handle a 7am class and know-it-alls in the back always interrupting the teacher and trying to show off in class…
There are enty of books you can read. If you’re really interested in learning I suggest you may start learning how to write bash.
For the rest I really would say, that just try doing stuff. Try to set up a docker, or other stuff. Also you can go to already solved Problems and try to understand what the problem was and what they did to solve it.
Also: Just start trying to support people. Google(or any other Search Engine of your liking) is very useful for this. Even if you just find out what exactly the problem is, that helps.
thanks. i have a laptop i deliberately installed debian on… but that’s about it lol
i’ll take you up on the support suggestion too… i recently had to figure out why a unix server went down at work. luckily we had a set of scripts and commands archived from the manager that supported it before he left. all i did was just run them with a little bit of logic and context applied, but it forced me to poke around a bit and seeing what each command did. i was careful enough not to break anything but i found it quite interesting