Hot answers tagged permissions
As you can see in your ls output, the .git directory is owned by root, and you don't have write access to it. Fix it with this command: sudo chown -R wiktor:wiktor /var/www/html/apps/blog/.git This will transfer file ownership of the git directory and everything in it back to you.
It seems like you messed up some file ownerships while running GUI applications as root using sudo. The following command should fix this and give you back the ownership of all files in your home directory: sudo chown -R $USER: ~ Hope this fixes it. For the future: Never run GUI programs as root using sudo - always use gksudo or at least sudo -H to ...
You can change the ownership of files using the chown command. Run man chown to read the documentation. In short, you can use it as sudo chown USERNAME:GROUPNAME file. BUT: I would not recommend changing the ownership of file outside your home directory! See Changed owner of /usr/bin and Changed permissions of / to user to see what happens when you do it.
To copy a file into /usr/bin you need sudo rights sudo cp katoolin/katoolin.py /usr/bin/katoolin Why? Thats why: Run stat /usr/bin/ and you will see something like this File: ‘/usr/bin/’ Size: 135168 Blocks: 272 IO Block: 4096 directory Device: 801h/2049d Inode: 1966082 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) ...
First: use sudo the way it is intended to be used in Ubuntu: for each command that requires it, no more. Don't use sudo to run a command unless it needs to be root. For example, most users would only need sudo for installing things. Second: use sudo -i if you need a root shell. Have a look at this Unix & Linux post to see the effect of various ways of ...
Only top voted, non community-wiki answers of a minimum length are eligible