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
Use tee –append or tee -a. echo ‘deb blah … blah’ | sudo tee -a /etc/apt/sources.list Make sure to avoid quotes inside quotes. To avoid printing data back to the console, redirect the output to /dev/null. echo ‘deb blah … blah’ | sudo tee -a /etc/apt/sources.list > /dev/null Remember about the (-a/–append) flag! Just tee … Read more
The problem is having wrong mod on the file. Easily solved by executing – chmod 400 mykey.pem Taken from AWS instructions – Your key file must not be publicly viewable for SSH to work. Use this command if needed: chmod 400 mykey.pem 400 protects it by making it read only and only for the owner.
Your command does not work because the redirection is performed by your shell which does not have the permission to write to /root/test.out. The redirection of the output is not performed by sudo. There are multiple solutions: Run a shell with sudo and give the command to it by using the -c option: sudo sh … Read more
This looks like a permissions issue in your home directory. To reclaim ownership of the .npm directory execute: sudo chown -R $(whoami) ~/.npm
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 … Read more
The keys need to be read-writable only by you: chmod 600 ~/.ssh/id_rsa Alternatively, the keys can be only readable by you (this also blocks your write access): chmod 400 ~/.ssh/id_rsa 600 appears to be better in most cases, because you don’t need to change file permissions later to edit it. (See the comments for more … Read more