In bash, type is a shell builtin command where as which is a script.
So, using type is more preferable.
Also, some history and more.
1027 /usr/local> type which
which is aliased to `alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde'
1028 /usr/local> type type
type is a shell builtin
Rewrite rules defined outside <VirtualHost> are not applied to the virtual host.
Add the following line inside the <VirtualHost>
When you log in to the system, bash will first execute the global setup file /etc/profile and then it will look for the personal setup file in the following order (will stop on the first finding)
- ~/.bash_profile (Derived from the Bourne Shell’s file name .profile)
- ~/.bash_login (Derived from the C Shell’s file name .login)
If all 3 files exist and need to be used, source the other files from ~/.bash_profile
~/.bashrc will be executed when you run a subshell by typing bash on the command line.
If ~/.bashrc needs to be executed when you log in to the system, source the file from ~/.bash_profile
Wildcards will only expand to match the names of the files in the working directory.
will list all the files in the working directory
But brace will expand regardless of the file existence.
will always echo
Good to note:
- How promises were chained with array.reduce
- How spawn helper function was used with generator to mimic the asyc function
ES7 async functions
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.
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
Adds extra IP addresses to a network interface
eg) ifconfig eth0:1 18.104.22.168 up
For example, ifconfig eth0:0 10.0.0.10 adds the address 10.0.0.10 as a virtual IP address to eth0
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.
… In fact, each
RFC has a status, relative to its relation with the Internet
standardization process: Informational, Experimental, or Standards
Track (Proposed Standard, Draft Standard, Internet Standard), or