When I start fucking with chmod, it happens way too often that what I want to do only works after I executed chmod 777...

May I interest you in a nice “chown”?

700 cause I’m selfish.

chmod -R 777 /

Why the fuck am I still getting permission errors

If you don't add the leading digit (out of respect) for the sticky/setgid/setuid bits, do you even Linux?

sudo

700 is the only sane answer for directories inside $HOME.

chmod 666 so only the devil can execute it

u=rwX,g=rX,o=rX because this won't make every file executable, only folders.

Nah, there’s a lot of config files in there that other programs need to read.

this but in reverse 🤷‍♀️

Unfortunately. I really wish $HOME was reserved for files I create myself. I know. I can create my own shit for that. But, I really wish every single random project I download to fuck around with didn't drop a config directory or file in there. ITS MY HOME.

But those are different

Yeah, not only does +x leave read/write permissions untouched, it also only makes it executable for the user, not for everyone and their cat.

I like to chmod it chmod it

Dont forgot setfacl

I mean, having config files in there makes a lot of sense. It allows you to move your home to some other machine/install and immediately feel at home, because everything is configured to your liking.

Now, the fact that many apps create their own directory instead of putting their stuff in ~/.config is pretty annoying.

Cat doesn't execute anything tho, it just reads and gives output

chmod -R 600 ~/, because I dont trust anyone, not even myself.

Looks like a handy flag

macOS by default makes /Users/* only readable by the owner, except for $HOME/Public, which is drwxr-xr-x, and $HOME/Public/Postbox, which is drwx-w--w-

Selinux

Had to be done for the joke. :)

I forgor the tilde and its taking a long time. wat do

chmod -R 777 / galaxy brain

Also for multi user systems it's handy that each user gets their own configs

sudo rm -rf / --no-preserve-root

Start from scratch

The cat command executes the cat program.

Nope, +x for life

Chmod 777 I live erratically without consequence.

chmod 755 for when setting permissions to directories. chmod +x for making something executable right when I am about to run it.

I don't use chmod nearly often enough to remember these numbers. I know there's a mathematical way to figure it out, but I cba to do that when u+wrx more or less tells me exactly what it does (grant the User Write, Read, and eXecute permissions)

The programs usually run in user context and have access to the files.

Even if thinking very hard I cannot come up with a scenario where a program that does not run in user context needs access to user files.

What happens when u try to cat the cat program, is that considered reading or executing

Usually, but there might be services running as other users that reference those configs. It really just depends on what’s on your system. Obviously you can make 700 work, but it might require tweaking some stuff.

It really just depends on what’s on your system.

Yes, this is what I wonder.

I use Linux since ca. 2005 and never ever had a program not working because it could not read a user’s $HOME contents.

Tilde is a shortcut to /home/palordrolap

Except if you use kitty terminal emulator with unsecure remote access. Issue

Then with cat, you could execute arbitrary commands...

Both, they are not mutually exclusive.

chmod -R -x *

chmod -R ug+rwX,o=r *

Careful: chmod -X also looks for any existing exec bits:

$ umask 0
$ >foo >bar
$ ls -al foo bar
-rw-rw-rw- 1 user group 0 Sep 10 00:00 bar
-rw-rw-rw- 1 user group 0 Sep 10 00:00 foo
$ chmod o+x foo
$ ls -al foo bar
-rw-rw-rw- 1 user group 0 Sep 10 00:00 bar
-rw-rw-rwx 1 user group 0 Sep 10 00:00 foo
$ chmod u=rwX,g=rX,o=rX foo bar
$ ls -al foo bar
-rw-r--r-- 1 user group 0 Sep 10 00:00 bar
-rwxr-xr-x 1 user group 0 Sep 10 00:00 foo

You can actually do chmod +777,u+rwx,go-w foo to make the logic easier if you want to force a starting assumption.

Yeah. That's more my frustration. That it's implented poorly by most people. I don't think that trying to change the standard by "adding another standard" would be helpful. Just minor frustration. Which usually leads me to putting all my organized directories and shit in a dedicated location. And I just let /home be the clutter that it is.

real question is how do you pronounce chmod

c h mod

I pronounce it chmod, you?

shmod.
and then cho-wn (ch'own? cho-un?)

and of course, hweel (jk on this one)

"c h m o d"

Just like "l s" and "p a c m a n"

This is exactly what I expect, so I never got tripped up by this. But yes, it's worth pointing out that this will expand the executable flag on files that are already executable and set it on folders too. But not set it on files that aren't executable at all.