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)
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.
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.
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.
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.
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-
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
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.
73 replies
not giving a fuck about proper file perms is fine as long as its not a server
This is drake erasure and I'm LOVING EVERY MINUTE OF IT, JERRY
Yo dawg, heard you like memes
Why? I mean not Drake because Drake sucks
My specify every permission every time? That's just going to create arrows.
But those are different
Yeah, not only does
+xleave read/write permissions untouched, it also only makes it executable for the user, not for everyone and their cat.If your cat isn’t the first entry in /etc/sudoers I’m not sure I want to know you
Cat doesn't execute anything tho, it just reads and gives output
Or am I???
x='dumb.txt' && echo "ls | grep $x && cat $x && rm -v $x" > $x && cat $x | bashThe cat command executes the cat program.
What happens when u try to cat the cat program, is that considered reading or executing
Both, they are not mutually exclusive.
Except if you use kitty terminal emulator with unsecure remote access. Issue
Then with cat, you could execute arbitrary commands...
If your cat isn’t the first entry in /etc/sudoers I’m not sure I want to know you
Had to be done for the joke. :)
chmod 666 so only the devil can execute it
this but in reverse 🤷♀️
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”?
chmod -R 777 /Why the fuck am I still getting permission errors
sudo
Selinux
You can actually do
chmod +777,u+rwx,go-w footo make the logic easier if you want to force a starting assumption.Nope, +x for life
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)
4 read, 2 write, 1 execute.
That's it. Add them up for whatever you want.
and digits are sticky, owner, group, all
chmod -R 777 /galaxy brainchmod -R 600 ~/, because I dont trust anyone, not even myself.I forgor the tilde and its taking a long time. wat do
sudo rm -rf / --no-preserve-rootStart from scratch
Tilde is a shortcut to /home/palordrolap
False. It's a shell synonym for /home/ah-ha-ha-nice-try-you-are-not-getting-my-real-homedir-name
... it's a PITA to type out longhand, let me tell you.
Ah, I see. I thought that you had forgotten what the tilde does, not that you ran the command without it!
I was being a silly goose and pretending I was more clueless than I actually am.
(Probably not by as much as I'd like to think.)
chmod -R ug+rwX,o=r *
Such a beautiful language.
If you don't add the leading digit (out of respect) for the sticky/setgid/setuid bits, do you even Linux?
700 cause I’m selfish.
700 is the only sane answer for directories inside
$HOME.Nah, there’s a lot of config files in there that other programs need to read.
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.
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.
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.
Also for multi user systems it's handy that each user gets their own configs
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.
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.
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
$HOMEcontents.macOS by default makes
/Users/*only readable by the owner, except for$HOME/Public, which isdrwxr-xr-x, and$HOME/Public/Postbox, which isdrwx-w--w-I gotta ask why they put Public in home
Because it's a user-specific folder that says "This is mine, but you can see it."
real question is how do you pronounce chmod
hmod
Shmaude
“change mod”
"chemod"
shmod. and then cho-wn (ch'own? cho-un?)
and of course, hweel (jk on this one)
The CH from channel and then mod
"c h m o d"
Just like "l s" and "p a c m a n"
I pronounce it chmod, you?
i say c h then mod
I pronounce it the way it's written.
chmod 755for when setting permissions to directories.chmod +xfor making something executable right when I am about to run it.Chmod 777 I live erratically without consequence.
I like to chmod it chmod it
u=rwX,g=rX,o=rX because this won't make every file executable, only folders.
Careful:
chmod -Xalso looks for any existing exec bits: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.
Looks like a handy flag
chmod -R -x *
Dont forgot
setfacl