Disclaimer: Do not run this command.
definitely nsfw
this post was submitted on 27 Jun 2025
461 points (97.1% liked)
linuxmemes
26027 readers
215 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
I did chmod -R 666 / when I started playing with Linux in 1999. It did not end well.
Sudo didn't really exist back then, you ran things as root like real men. /s
(sitting cross-legged on the floor drinking a juice box) "How DID it end, grampa?"
6 permission mean read+write, but no execution rights. So you cannot execute any commands and system bricks itself.
Sorry, that's a huge turn off. Filesystem perms exist for a reason and should be respected
Yeah, this is modern day slutshaming
Made me puke in my mouth
Back in my early days of Linux I ran this exact command, I forget why, but for some reason my WiFi stopped working immediately after and then SELinux started yelling at me for some reason. I tried to fix SELinux and most certainly commited an innumerable amount of cardinal sins.
I had to reinstall whatever distro I was running at the time
I accidentally did this on a work computer, just going with tab completion. Things started to break very quickly. I don't think I could even run sudo or rm lol. Total wash. Had to reinstall (this was on my first week in office - so embarrassing!).
Is a woman telling you:
"you can do whatever you like, but so can my Ex your mama and the Dallas cowboys."
Really that much of a male fantasy?
Missing setuid. You have just bricked your system good job
Obligatory DO NOT RUN THIS ON YOUR COMPUTER (or anyone else's).
You'd think with fully open permissions, everything would work better, but many programs, including important low level things, interpret it as a sign of system damage and will refuse to operate instead.
If you do run it, you'd better have a backup or something like Timeshift to bail you out, and even if you do have that, it's not worth trying it just to see what will happen.
It's not quite as bad as deleting everything because you can boot from external media and back up non-system files after the fact, but the system will almost certainly not work properly and need to be repaired.
You have been warned.
One time I introduced someone to Linux then left them to their own devices.
I returned to them hours later to find out they had gotten annoyed with permissions errors and run chown -R ${THEIRUSER}: /.
The results were not what they wanted.
A valuable lesson
I did this once by accident (bad scripting, managed to abort it,) it wasn't too bad until sudo told me that the sudoers file had the wrong owner. I then learnt that there are other ways to become root.
OS ran for another ~6months after I re chowned etc to root.
Wow. You were lucky. That abort might have been what saved you there.
Someone actually ran it on a server at my workplace, trying to fix file permissions on a samba share. Broke SSH and the samba daemon. Thankfully I was able to fix by removing the permissions from the config files the error logs pointed to.
Just saying, I think it was a ChatGPT idea, other people use it every day. I only use it if I'm completely stumped, and only take it as suggestions.
What exactly does that command do
It sets permissions (ch ange modification rights) on all files (-R = recursive, stepping down through directories) in the file system (hence starting at /) so that they can be read, (re)written and executed as programs by all users (the 777 part). 000 would be no permissions for anyone (except for the root user), which would be just as bad.
Excellent summary. Just as a bit of trivia I'll add that Linux file permissions go like r w x (read write execute) = 4 2 1, so taken all together a 7 means the indicated user can do all those operations.
And yeah, it breaks your system in surprising ways. Most people would just have to start over.
gives all users on the system read and write access to any and all files and resources
New guy at work ran this to try to fix permissions on his home folder, accidentally ran it on root (both would have been bad)
Several highly paid and experienced Linux admins finally just gave up and deleted the server and built a new one from the backups.
Why does he have rights to use sudo in the first place?
Which, honestly, is the better way to go. Treat your compute resources like cattle, not pets.
One of our servers is a rotting carcass being kept alive by our collective prayers. It runs Windows 7 and custom software whose developer is dead and the source is missing, nothing has been updated for over a decade, and it has its own independent UPS because once it goes down, it has an extremely slim chance of recovering, and we're afraid to test it. It controls the card entry system into the building, including the server room. Boss doesn't want to replace it because we'd have to replace all of the terminals and controllers too, and it hasn't catastrophically failed yet.
You're right. It's not a pet. It's like one of the Saw movies: if it dies, we're all fucked.
So... the dead server controls who is even able to enter the building? Wow. That is one big juggernaut of a problem heading for you.
Typically a brick can control who can enter the building. Security man the doors for a few days until the new system is in.
The question I often ask clients who think this way is "How much would it cost if it did fail? Let's say this happened today. What would be the cost to replace it NOW and not only that but make sure people who are working can still do so with the interruption?
Now how much would it cost to schedule the interruption and manage the fall out in a way that is controllable?
For some, the catastrophic failure points to "hey I fixed the thing!" And the incentives for that kind of person are different from the person whose job is to mitigate risk.
It sounds like your boss is the former. In which case it's going to be fun when it fails.
I gΓΆnne be honest, it sounds kinda stupid to be reliant on a server to open the door to the same server.
It's surprisingly easy to get from the main hall to the server room. There are two doors between the entry hall and the server room, one can be bypassed by yanking it real hard, and that gives access to the breaker box for the electromagnets among others. The building is not particularly well-designed.
I'm sure there's a good reason (or at least a believable reason) but I'm curious now, why can't copies be made of the binary/data and start trying to get it running on a VM or another box?
The reason is that we want it to fail. My original comment was more emotive than descriptive. The system is horribly designed and a fucking menace on the best day, so short of direct sabotage, we're doing what we can to force the bossmang to replace it.
load more comments
(1 replies)
I will make a disclaimer. Thanks.
load more comments
(1 replies)
asexuals and demisexuals be like sudo chmod -R 700 /
Doms with cuck and denial fetishes have partners like
sudo chmod -R 077 /
load more comments
(1 replies)
If I wanted Windows perms I would have installed Windows
Windows perms are pretty locked down though. Sometimes I can't delete my own files because I need permission from "Administrator" :/
You can actually use Windows-style permissions (ACLs) on Linux via setfacl.
load more comments
(2 replies)
Most Linux filesystems, being case sensitive, won't find the SUDO command.
With alias all things are possible.
alias SUDO='sudo rm -fr / --no-preserve-root'
If you shout at your shell, it refuses to listen
CHMOD command does not exist either. It's just the meme's font that is in all caps.
load more comments
(1 replies)
Taking the term open sourced to a whole new level!
Everybody has permissions!
It's still not really open-source until you open up all the ports now don't you think?
view more: next βΊ