When blame shows every line being changed and not committed state

00000000 (Not Committed Yet 2016-06-12 12:28:55 +0900 1) …
00000000 (Not Committed Yet 2016-06-12 12:28:55 +0900 2) …
00000000 (Not Committed Yet 2016-06-12 12:28:55 +0900 3) …
00000000 (Not Committed Yet 2016-06-12 12:28:55 +0900 4) …

This happened on Windows machine with Linux repo.

http://stackoverflow.com/questions/4638500/git-blame-showing-no-history

The problem is due to the different line breaks used in local machine and the server.

This can be solved by blaming on a file in the repo (since the file would have the same line breaks)

git blame HEAD file.txt

or using -w flag to ignore the line breaks.

git blame -w file.txt

SELinux

SELinux (read as S.E.Linux)

The main purpose of using SELinux is to protect the system from “unpredictable” security breaches.
It provides a kernel-level security protection based on a white-list policy and can protect from things like application bugs and application misconfigurations.
(Buggy/misconfigured FTP/HTTP/other daemons may give the users more privileges than they should)

When troubleshooting SELinux related permission issues, “ls -Z” is the command to view the “label”, which defines the access privileges.

When “which” command and the actual executable being executed do not match

Problem:

[root@clnt2 bin]# python -V
Python 2.6.6
[root@clnt2 bin]# which python
/usr/local/bin/python
[root@clnt2 bin]# /usr/local/bin/python -V
Python 2.7.3

[root@clnt2 local]# hash -r
[root@clnt2 local]# python -V
Python 2.7.3

http://unix.stackexchange.com/questions/47363/my-which-command-may-be-wrong-sometimes