Can I do this?
sudo chown -R myUsernName /usr/lib
I mean can I do this without worrying that my OS will be broken? Or permissions will be screwed up?
Here is the reason why I would like to do it
and here is why I don't and I came here to ask you guys:
Two things:
(1) There is absolutely no advantages for this. The files in /usr/lib are supposed to be owned by root/system, as MANY things on the system which are owned by root are dependent on them.
(2) This is also a very good way to break your system.-
Just to make a point, follow this general rule of thumb:
If in doubt, don't do it.
Given that sudo is /usr/bin/sudo normally, you won't be able to use it after you run that chown command: the sudo binary owner will be yourself, so you won't get root permissions when running it next time.
So don't do that.
/usr/lib/
No.
If you don't completely understand the reasons for the permissions of the files on your system, don't change them.
Generally speaking, files outside your home directory or /tmp or designated directories for data should belong to system users, not to you.
Furthermore, you should not write under /usr, with the exception of /usr/local: this is reserved for your distribution or package manager. If you want to install a program system-wide, install it under /usr/local.
That installation script looks like it's trying to install in the wrong places. If it tries to copy things to /usr/lib, it's broken. Don't use it. Look for a package for your distribution, or for a better installation script, or better installation instructions. Again, if things end up in /usr/lib (as opposed to /usr/local/lib) without going through a package manager, the installation process is broken.
/usr WILL LIKEWISE BREAK YOUR SYSTEM. Don't do it. Worst case senario, download the script and edit it to change all the paths to something else before you run it. Best case, find a real package that installs in your user folder or /usr/local.
No, it is not safe: the permissions in /usr/lib are chosen for two reasons:
You can see the latter using
find /usr/lib -type f -perm /7000
to search for any program using setuid (4000) or setgid (2000) or sticky bit (1000). On my Debian7, that shows several files:
/usr/lib/eject/dmcrypt-get-device
/usr/lib/dbus-1.0/dbus-daemon-launch-helper
/usr/lib/kde4/libexec/kdesud
/usr/lib/openssh/ssh-keysign
/usr/lib/libvte9/gnome-pty-helper
/usr/lib/emacs/23.4/x86_64-linux-gnu/movemail
/usr/lib/mc/cons.saver
/usr/lib/libvte-2.90-9/gnome-pty-helper
/usr/lib/utempter/utempter
/usr/lib/pt_chown
/usr/lib/evolution/camel-lock-helper-1.2
/usr/lib/policykit-1/polkit-agent-helper-1
If you change the ownership of those files, they can no longer perform the task for which they are designed. For instance, gnome-pty-helper and utempter are used to update the utmp/wtmp feature (providing data for w and last).
Further reading:
chown, do you mean this forchmodorchown?