First of all a minor terminology nitpick: chmod doesn’t remove permissions. It CHANGES them. Now the meat of the issue — The mode 777 means “Anyone can read, write or execute this file” – You have given permission for anyone to do (effectively) whatever the heck they want. Now, why is this bad? You’ve just … Read more
You need to either be the owner of the file or be the superuser, i.e., user root. If you own the directory but not the file, you can copy the file, rm the original, then mv it back, and then you will be able to chown it. The easy way to temporarily be root is to … Read more
Use chown to change ownership and chmod to change rights. use the -R option to apply the rights for all files inside of a directory too. Note that both these commands just work for directories too. The -R option makes them also change the permissions for all files and directories inside of the directory. For example will change ownership (both user and group) … Read more
The other answers are correct, in that chmod -R 755 will set these permissions to all files and subfolders in the tree. But why on earth would you want to? It might make sense for the directories, but why set the execute bit on all the files? I suspect what you really want to do is set the … Read more
chmod a+x modifies the argument’s mode while chmod 755 sets it. Try both variants on something that has full or no permissions and you will notice the difference.
The other answers are correct, in that chmod -R 755 will set these permissions to all files and subfolders in the tree. But why on earth would you want to? It might make sense for the directories, but why set the execute bit on all the files? I suspect what you really want to do is set the … Read more
If you are going for a console command it would be: chmod -R 777 /www/store. The -R (or –recursive) options make it recursive. Or if you want to make all the files in the current directory have all permissions type: chmod -R 777 ./ If you need more info about chmod command see: File permission