lol sudo rm -rf / - Feddit

Why would you tell people to run that command?
It removes the french languagepack

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
Ok you made me spit out my drink. Good job.
You deserve points for creativity
Yeah, I don’t know if it’s recursive or even if it even accepts wildcards but it’s probably best if it doesn’t work.
Sudo: command not found
Isn’t auto capitalization a bitch 🫠
if one would fall for this, do you really think that they know how to backup and restore backups?
I am not bullshitting with this: I had a classmate A and classmate B just last year, where A jokingly mentioned to B to do a rm -rf /* for a class project on a VM. I could not believe it myself, but B actually did it and laughter ensued… Luckily B has a VM backup.
don’t need –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.

It’s a joke dude, on my part, and I’m sure on OPs part.
it may be a joke answer, but then there are those described by the commentor who take joy and glee from it.
Yeah, but it’s posted in Linuxmemes, if it were posted anywhere else I would warn people about running the command.

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.

:(){:|:&};:
Now that’s a weird way you like oral sex…
Do you not use the “ampersand” when “dining at the Y”? Prude. It’s perfectly safe with the proper preparation. Don’t believe the rumors, they’ve got all the signs of a moral panic.
Classic fork bomb

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.

What is Fork Bomb in Bash? Understanding :(){ :|:& }

The random looking symbol sequence :(){ :|:& };: could bring a Linux system down. It's called fork bomb and here's how it works.

It's FOSS
cheers mate. it’s a virus because its copied all over ✌🏽 part of the artwork concept
I trolled myself by “learning” that I could delete all files in a directory, including hidden files, with rm -rf ./*. The mistake being that I (more than once…) accidentally put a space between the . and /.
And that's why every rm command should start life as an ls command and then change the command and options while not touching the target directory. Takes a little longer, but saves so much hassle when you do fuck up.
Rm was updated to actually log a warning in the -rf / cases, so that’s less likely to happen anymore. Still not a bad habit to use ls though
/* still works I think
not if you use /*. 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.

I just alias rm to trash and if I really want to remove something I just escape the alias: \rm
Could do that, but they have different flu args.i respect the power of rm now.
Something something rm -fr / to remove the french language pack
and rm -rf removes only the République française language pack
other ““french”” species are inferior and don’t deserve mention

honestly I’ve had the best luck when I use the French Riviera version to delete my hard drive:

rm -Riv /

rm -fr /*
newer versions of coreutils require --no-preserve-root on /* too
That’s the only one I find particularly funny
Also you don’t want to preserve the word roots of it so you have to add --no-preserve-root
command -v lol is returning an error on my system???

Ok now type “touch /this”

And then hum the famous M C Hammer song.

the people who troll or make fun of linux beginners are the same people who wonder every year why desktop linux isn’t more mainstream
And 80% of these are on Lemmy, I mean put up a question or comment that how Linux is not helpful is simple tasks such as giving permissions to program without using command prompt , will get you downvotes/ you are idiot comments heavily.
Yeah it’s pretty bad
never had anything quite as bad, there are a lot of people commenting “JuSt SwiTcH tO LiNuX” and never answer when you explain how you’ve tried to switch but sim racing, CAD and many other things are way too complicated to get running reliably.
I wish I could help people like this but I get really frustrated when they don’t understand something I say for the first time, or are generally bad with tech, and I don’t know how to get over it

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…

systemd by example - the systemd playground

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

The best places I learned from were installing gentoo in a vm and separately linux from scratch for the more advanced stuff. Though I learn more from doing than reading personally
I asked for help on the Discord server of LinuxServer.io and they were literally talking shit about me to each other while I was in the chat because I didn’t understand their utter garbage documentation for a Docker I was having trouble with, even with a CS degree.