You can’t cd or ls in a folder if you have no +x permissions on it. That is all. I wasted 3 hours of my life.

@unsaid0415@szmer.info · 1Y

You can’t cd or ls in a folder if you have no +x permissions on it. That is all. I wasted 3 hours of my life.

@30p87@feddit.de · 1Y

Yup. Took me weeks to figure out why I explicitly need to use sudo nvim for my nginx config on my Pi, while on my server my little helper script could automatically use sudo for me. Turns out, I chmoded the sites-available and sites-enabled on my pi to 644 but left them untouched on my server.

I still don’t know what numbers would be 644 but with execute permissions, but in the end, idc.

Undearius · edit-2 1Y

For those that don’t know, you can use three numbers, zero through eight, with the chmod command. it takes the binary of each digit to set the permissions.

$ chmod 644
 6  |  4  |  4
110 | 100 | 100
rw- | r-- | r--

@merc@sh.itjust.works · 1Y

with the chmid command

Nah, that command just makes the file below average quality. It’s a new command added by Gen Z.

@merc@sh.itjust.works · 1Y

644 and 755 are the two most useful octal codes to remember because they make up the majority of files on your system. 644 is user read/write but read-only for everyone else. 755 adds execute to that, useful for scripts and directories.

Other than that, the most common other things are setting access for group and others to zero, so your ~/.ssh directory is 700 (rwx for you, no access for anyone else) and the private keys in it are 600, rw for you, no access for anyone else).

Jamie · 1Y

Execute just adds 1, so if you want the dir world viewable, it’s 755.

@GenderNeutralBro@lemmy.sdf.org · 1Y

You can also do chmod +x to add the executable bit to whatever the existing perms are.

0: no permissions
+4: read
+2: write
+1: execute

🇨🇦 tunetardis · 1Y

I often go chmod -R go+rX . if I want to give read-only access to whatever I’m working on to everyone else. The capital X only sets the executable bit on directories.