this post was submitted on 05 Mar 2025
60 points (100.0% liked)
linuxmemes
23841 readers
784 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
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
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.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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't get it
Read/write/execute file permissions.
Having them set incorrectly can cause problems, such as creating a file as root then leaving you unable to modify it as user, being unable to execute a script because execute is not set, or being unable to use your SSH keyfile because you left the permissions too open.
It's more actually like "Why is it, when something doesn't happen, is it always you three"
It's the Linux file permissions. If something doesn't work properly, it's often due to wrong permissions because the app can't save/read it's stuff
Maybe the recent events had something to do with ye good olde
chmod 777
Was 700, should have been 755... 777 is more like the "just put sudo in front of the command" nuclear option.
I had a fuckup by qualys recently that basically did what you described on many of our RHEL machines, broke a few things.